Wi-Fi devices on every access point, minute by minute, lined up with the published schedule. Talks ranks sessions, Crowd shows how people moved, Network is for NetOps. A device count is a proxy for attendance, not a headcount; read the method notes before quoting a number.
DayScore by
Room timelines
By time block
Four Winds bridge sims by hour
Average devices on AP 3-12 (L3 east hallway, on the Simulators switch) for each clock hour. Missions run back to back, about 30 min each, so hours are the unit here, not sessions. Bright underline = open hours (Tue-Thu 10:30 to 5, Fri 8 to noon); faded = outside them. Not ranked against talks.
Leaderboard
Every scheduled session with Wi-Fi coverage. Click a column to sort. Day filter above applies.
Show
What drew a crowd
Main-track talks only, scored vs room norm (1.00x = a typical talk in that room, so Ballroom B isn't penalised for its two APs). Each dot is a talk; the tick is the median. Topic, level and length come from the schedule. All days.
Small groups: Policy/Procedures is 5 talks and Advanced is 2. Treat those medians as hints, not findings.
Sessions that ran more than once
Same title, run on different days or times. Bars are average devices per run, in order. All days.
Arrivals and departures
Every device on con Wi-Fi, venue-wide, 5-minute averages. Dots mark when each day reached half its peak on the way in.
Tuesday includes registration and first-day arrivals. Friday is cut short by closing and teardown (APs unplugged from about 11:45).
Break tide
Devices per floor, minute by minute. Shaded = keynote and lunch. Ticks along the bottom = main-track changeovers.
Lunch, by floor
Before = 11:40-11:55, during = 12:15-12:45, after = 1:40-2:00. When the total drops, devices left con Wi-Fi: people went out for lunch, or phones dropped off.
Keynote capture
Where the con's devices were during each keynote and ceremony (scored window). The percentage is the ballrooms' share of all devices on site.
Mid-talk shifts to the foyer APs
Moments during a main-track talk when a ballroom's APs lost 25+ devices within a few minutes and the Level 2 foyer APs (2-10, 2-11, 2-12) picked up a big share of them. Either devices roamed to a louder AP, or people stepped out into the foyer. AP counts alone can't tell which.
Ask Arista: radio events (channel changes, DFS, radio-management runs) and client roam logs for these timestamps would settle it. For the committee: this is why the page doesn't score whether a talk "held the room": a ballroom can lose 30 to 40 devices mid-talk whether or not anyone left. Also seen: Tue 4:13-4:19 PM no data at all, then Level 1 and 2 came back at about half their devices and Level 1 recovered within minutes. That window is left out of every score.
AP load
Every placed AP, Tue 7 AM to Fri 3 PM. Bar = con peak (busiest minute). Notch = 95th percentile during 9-5. Right column = minutes at 100+ clients. The 100 line is a reference, not a hard limit.
Internet vs the schedule
Per-minute WAN bytes come from netdash's wall-board table, which starts Wed 11:38, so the table and the per-device finding cover Wed 11:38 to Fri only. Hourly data can't separate talks from changeovers. Down and up are Centracom only (Starlink carried about 1 GB all week). Changeover = within 4 min of a main-track start or end.
Method and caveats
Where the numbers come from. netdash polled CV-CUE every minute and stored associated clients per AP (ap_minute, export 2026-10-31 19:11 UTC). Each session is matched to the APs inside its room on the V2 AP plans. A session's score uses the minutes from 5 min after start to 2 min before end, so arrivals and departures don't count.
Avg devices: mean devices on the room's APs over those minutes.
Peak: the busiest single minute.
vs room norm: avg divided by the median session avg in that room. 1.00 = a typical session for that room, 2.00 = twice that. Use this to compare rooms with different AP coverage.
Caveats
Devices, not people. Phones and laptops on Wi-Fi only. People on cellular, or with Wi-Fi off, are invisible. Thursday's census found about 1,400 devices at peak; plan on 1.3 to 2 devices per person.
APs don't stop at walls. On 5 GHz, 2-03 (north wall of A, faces the AI Maker Corner foyer) and 2-07 (south wall of C) ran at 28 dBm and pull devices in from the foyer and corridor. A and C read a bit high, B a bit low.
Ballroom B has only two APs (2-05, 2-06, both on the west wall). Raw counts understate B, so compare B to A and C with vs room norm.
†Before Wed 11:30 2-02 (A) and 2-13 (C) weren't installed yet. Most of their devices landed on neighbouring APs in the same room, but A and C may read a little low before then.
Devices shift between APs. 22 times during main-track talks, a ballroom's APs lost 25+ devices to the Level 2 foyer APs (mostly 2-10, the loud south-east one). That's either roaming or people stepping out, and the data can't tell which, so there's no "held the room" score. Details on the Network tab.
Gaps. Five partial polls and a Tue 4:13-4:30 PM Wi-Fi event are left out of every number.
Expo classrooms (Community Classroom 1 and 2) each share one AP with the open expo floor, so their numbers include passers-by. Treat them as rough.
Bridge sims use AP 3-12 alone. It hears the crew, the check-in queue, and people passing the east stairs, plus a few devices that never leave: about 1 to 4 overnight, and 10 to 20 in the evenings after close. Treat it as "how busy was the sim corner", not crew count. Open hours are assumed to match contests open, since the site only says "the conference's open hours".
Monday is thin. Training-day Wi-Fi counts are single digits to high teens per room. Many trainees were on wired, cellular or not yet on con Wi-Fi, so rank the trainings against each other only.
* Times the schedule doesn't list are assumed to be 8:00 to 4:30, like the other trainings.
Hyatt Place rooms (LAN party, evening events) have no con Wi-Fi and are left out, along with registration, the store, expo and contests open, and lunch.
Room to AP mapping (from the V2 AP plans overlaid on venue.json)
Community Classroom 3 is listed as "Cascade E". On the Tue-Fri L3 plan, the only seated classroom is the south-west room (Briefs, AppSec Jeopardy, keynote projection, and Briefs Community is scheduled in Classroom 3), so it maps to 3-08. Monday trainings are matched by title to the Monday L3 plan, because the room names on that plan and on the website don't line up.
Schedule scraped from saintcon.org/schedule (and /activities/four-winds) on 2026-10-31. 115 sessions matched, 31 skipped (no coverage, or not a session).
Type: Aldrich and Armata, SIL Open Font License 1.1, embedded for offline use. Colours from the SC26 Spaceways boards.