Short answer: the number of access points comes from concurrent devices, not from the floor area of the room. Cisco Meraki's high density Wi-Fi design guidance puts roughly 25 clients per radio and 50 per access point in dense deployments, and reduces the count to one division: concurrent 5 GHz clients divided by 25. At a 400 guest dealer meeting, assuming 1.5 devices per person, that is 600 clients and 24 access points. Line capacity is a separate calculation. In Türkiye there is a third item most teams miss: whoever hands guests an internet connection is an internet mass use provider under the regulation based on Law No. 5651, which brings a duty to keep access records. Below: the access point math, line capacity, the moments a network fails, isolating critical devices, who carries the 5651 duty and what to ask the venue.
How many access points do you need?
The calculation starts with concurrent devices, not square metres. Cisco Meraki's high density Wi-Fi design guidance recommends around 25 clients per radio and 50 per access point in dense deployments, and gives the device count as a simple division: take concurrent 5 GHz clients and divide by 25. The same document sets the threshold too. Once more than 30 clients land on a single access point, you are in high density territory. Put that against a real programme. A 400 guest dealer meeting at 1.5 devices per person is 600 clients, which the division turns into 24 access points. That is well above what sits in most hotel ballrooms, where the three or four units on the ceiling were placed with 60 person meeting rooms in mind. At a gala dinner, where most guests are eating and watching the stage, the concurrent share drops. If you run live voting, audience questions or a digital catalogue, the share climbs close to everyone in the room and the math has to follow.
How many Mbps of bandwidth do you need?
Access point count and line capacity are two separate calculations, and solving one while ignoring the other is the failure we see most often. Meraki's formula is application throughput multiplied by concurrent users. The per application figures in the same document: 500 kbps for web browsing, 1.5 Mbps for video conferencing, 768 kbps to 8 Mbps for HD video streaming and 8 to 20 Mbps for 4K. Say 250 guests are on social media and the web at the same time. That is 250 times 500 kbps, roughly 125 Mbps of aggregate demand. On top sit the sponsor booth video, the press uploading images and, if you have one, the live stream feed. Ask about upload separately. Guests post photos and video, so event traffic is not one directional the way home internet is. Before signing, find out whether the quoted speed belongs to your room or the whole building, and whether another event runs in the next hall that day.
How many people connect at once? Map the peaks
Total headcount misleads. What breaks a network is the peak, and four of them repeat in almost every programme: the check-in queue when doors open, the first five minutes of the opening speech, the return from the coffee break, and the moment the host says scan the QR code on screen. That last one is the hardest test, because everyone in the room tries to connect inside five seconds. Do not be conservative on device count either. A corporate attendee walks in with a phone, pulls a laptop out of the bag and brings a smartwatch onto the network. For planning, 1.5 devices per person is a reasonable start; at a training programme where everyone arrives with a laptop it passes two. Then there is the crowd nobody puts on the list: the build crew, catering staff, security and the stage technicians.
Why does event Wi-Fi collapse? Three common causes
First, the 2.4 GHz band. It offers only three non overlapping channels, 1, 6 and 11. Ten access points placed side by side end up sharing those three channels and taking turns waiting for each other. Meraki suggests a roughly 30/70 split between 2.4 GHz and 5 GHz, which means putting the weight of the load on 5 GHz. Second, channel width. The wide channels people open at home to gain speed do the opposite in a packed hall; Meraki recommends 20 MHz channel width for high density deployments, because narrower channels mean more non overlapping channels. Third, everything else transmitting in the room. A hundred personal hotspots, the router the sponsor brought along and wireless presentation gear running on 2.4 GHz all share the same air. Hardware generation genuinely matters here: OFDMA in Wi-Fi 6 fits several devices into a single transmission, and BSS coloring lets neighbouring access points tell each other's signal apart so that units on the same channel stop silencing one another needlessly. Ask which standard the venue's access points support. The answer usually reveals the age of the installation.
Keep critical devices off the guest network
Putting the working half of the event and the guest internet on one network creates a single point of failure. Check-in tablets, badge printers, card payment terminals, the live stream encoder and the LED screen media server should sit on cable wherever cable can reach. Where it cannot, build a separate SSID on a separate VLAN and keep guests off it. A per client speed limit on the guest network helps as well, so the whole room's bandwidth does not disappear into one laptop that decided to start a cloud backup. Split the broadcast line from day one. Pulling a cable on build day takes half an hour. Mid programme, there is no recovery.
Who keeps the access records under Law No. 5651?
In Türkiye this question has a written answer, and most teams hear it for the first time at the contract table. The Regulation on Internet Mass Use Providers defines a mass use provider as a natural or legal person who gives people the opportunity to use the internet at a given place for a given period. If you hand guests Wi-Fi in a ballroom, the definition covers you. Article 4 sets out three duties: use a content filtering system to block access to content constituting a crime, record access logs electronically in your own system and keep them for two years, and where you provide internet in areas open to the public, run a system that identifies users through SMS or a similar method. The regulation also spells out what an access record contains: the IP address assigned, start and end time of use, the device MAC address and destination IP information. In practice the cleanest route is to run guests through the venue's own hotspot platform and put the duty in writing in the contract. If you bring your own gear and open an SSID whose password everyone knows, the logging side is yours to build. If you collect phone numbers at the portal, the KVKK privacy notice belongs on the same screen.
Seven questions to ask before signing with a venue
Ask these in writing while collecting quotes. The answers show the real difference between venues. How many access points are installed in the room and which Wi-Fi standard do they support. What is the download and upload capacity of the line, and is it shared with other halls that day. Can a dedicated SSID and password be created for the event, and can a per guest speed limit be applied. Can you get a separate wired line, a separate VLAN and a static IP for broadcast and check-in. Does access logging and user identification under Law No. 5651 run through the venue's hotspot platform. Are you allowed to run a signal survey in the room on build day. If extra access points are needed, where do cabling and power come from. Run that survey once the chairs are set and crews are working, not on an empty morning: the human body absorbs 5 GHz signal, and a full room measures nothing like an empty one.
Draw the network plan next to the stage plan
A Wi-Fi plan costs less and works better when it is drawn alongside the stage and seating layout rather than after them. Where access points can go depends on decisions about truss, the LED screen and the rigging points overhead, and so do the cable routes. Tales Event works out of Istanbul and delivers dealer meetings, launches and congresses across Türkiye, and we size the network alongside the audio, lighting and video plan. Send us your headcount, the venue and the event app you plan to use, and we will come back with the access point count, the bandwidth you need and who carries which duty under Law No. 5651, on a single page.
Let's talk about your event
Tell us your idea and we will prepare the concept and quote.