--- title: "Stadiums and arenas monitoring | Nexus Observatory" description: "Stadium safety depends on how crowds move through gates, concourses and stands, and on weather that can turn dangerous. Entry counts…" url: https://observatory.global/industries/events/stadiums-arenas/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Events](https://observatory.global/industries/events/) / [Specialized fields](https://observatory.global/industries/events/fields/) / **Stadiums and arenas** # Every crowd and every storm, seen from the control room. Stadium safety depends on how crowds move through gates, concourses and stands, and on weather that can turn dangerous. Entry counts, crowd density from cameras, and site weather with lightning warning, joined in the control room, let safety officers act before crowding or storms become incidents. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Events **Measurements**: 4 **Sources cited**: 5 1. Events · Stadiums and arenas Crowds and weather Stadium safety depends on how tens of thousands of people move through gates, concourses and stands, and on weather that can turn dangerous within minutes. Safety guidance sets capacities and flow rates and puts the control room at the centre. It needs to see crowding and storms early. 2. What is measured Counts, density and storms Counters at turnstiles and gates measure entry and exit flow, cameras over concourses, stands and approaches measure crowd density, a thunderstorm warning sensor watches for lightning, and a weather station measures wind and heat stress for spectators. Each reading carries its time and its quality flags. InstrumentsGate counters · Density cameras · Lightning sensor · Weather station 3. The base node Counting without identifying The edge server counts people in each zone from camera images without identifying anyone, compares density and flow with the safety plan's limits, warns of approaching lightning and heat, and keeps an event log for review. Nothing is lost when a link drops; the node keeps it. 4. Radio and links Into the control room Venues have fibre, so cameras and counters reach the control room over it through a security gateway. On event days a private 5G network carries temporary cameras and stewards' devices. Each link is chosen for the place, not from a catalogue. LinksFibre · Private 5G 5. How it works From a crowded concourse to a held gate At half-time a concourse fills faster than it drains. Density passes the plan's limit; the control room holds an entry gate, opens a second route and sends stewards. Density falls within minutes, and the log records every decision. Every step is kept on the record. 6. From order to operation · Order Scope with the safety officer The scope reads the venue's safety certificate, capacities, zones, control room and past incidents. Nexus Observatory Inc. returns the sensing design, control room integration, privacy design and a price per venue and per year. Every assumption in the scope is written down and priced. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Survey zones and flows Crews survey gates, concourses, stands and approaches with the safety officer: camera positions for density, counter points, weather and lightning sensor sites and network paths. Findings are recorded with drawings. Every finding is kept with the site record for the crews who follow. 8. From order to operation · Permits Licensing and privacy The safety certifying authority is told of the system, privacy rules for cameras are agreed and published, and connections to the control room go through change control. Every approval is kept with the venue record. Approvals are tracked site by site, so nothing waits unseen. 9. From order to operation · Build Build and test Cameras, counters, sensors and the server are configured with zones and limits, enrolled with their identities and tested with recorded crowds before shipping. Test results travel with the kit to the site. Nothing ships until the whole kit has passed its tests together. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install between events Crews install cameras, counters, the weather station and lightning sensor between events, connect the server behind the security gateway, and add the views to the control room. Every point is recorded. The site record is updated before the crew leaves. 11. From order to operation · Commission Commission at a live event Each node proves its identity. Counts are compared with turnstile data and manual counts at a live event, density with stewards' reports, and lightning warnings with the regional service. Results are signed and kept with the site record. Acceptance is recorded with the owner before handover. 12. From order to operation · Operate Manage the crowd Safety officers see density and flow in every zone and approaching storms. Gates are opened or held, stewards are sent to crowding before it peaks, and spectators are moved from exposed stands when lightning approaches. Reports for owners and funders come from the same record. 13. From order to operation · Maintain Review every event After each event the log is reviewed with the safety team, limits and zones are adjusted, cameras cleaned and re-aimed, sensors checked and software updated in rings. Every review is kept. Spares and procedures travel with the crews. Maintenance history stays with each site for its whole life. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For safety officers and authorities Safety officers and stewards receive density and flow by zone; event control receives lightning and heat warnings; safety certifying authorities receive event logs; venue operators receive capacity reviews, each tied to zone and time. Each product carries its site, time and quality flags. [See the data products](https://observatory.global/data-products/) 15. Evidence Guidance for safe grounds Capacities and flows follow the guide to safety at sports grounds and crowd management guidance, lightning warning follows the thunderstorm warning standard, and heat stress the international index. Every event is logged for the safety certificate. Records are open to the people who must check them. Drawn againstGuide to Safety at Sports Grounds · HSG154 · IEC 62793 · ISO 7243 · WMO-No. 8 16. What you get Private Wireless as a Service Standalone private 5G or LTE for a site, campus, port or mine: radios, core, SIMs, spectrum route and operations. Delivered as managed service and hardware + software, for industrial operators, ports, campuses, venues, public safety. Scale: Per site; fleets of sites. [Talk to sales](https://observatory.global/contact/sales-enquiry/) 17. Next step Plan stadiums and arenas with us Tell us the site, the measurements and the rules it answers to. We reply with a survey proposal, a design and a scope for stadiums and arenas. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace. [Plan a deployment](https://observatory.global/contact/deployment/) [Open the Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) **01** The place and its hazards ## Where it runs, and what can go wrong. Operating contextSports grounds are licensed and managed under published safety guidance that sets capacities, crowd flow rates and the role of the control room, and managing crowds safely has its own guidance from health and safety regulators. Thunderstorm warning systems are specified by an international lightning standard. Hazards - Crowding at gates, concourses and exits - Surges and crushes in stands - Lightning and severe weather during events - Heat stress among spectators - Control rooms seeing incidents too late **02** What must be measured ## What, where, how often, and under which rules. Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below. | Measurement | Where | Cadence | Sources | | --- | --- | --- | --- | | Entry and exit flow | Turnstiles and gates | Continuous during events | 1 | | Crowd density | Cameras over concourses, stands and approaches | Every few seconds | 12 | | Lightning and storm approach | A thunderstorm warning sensor at the venue | Continuous | 3 | | Weather and heat stress | A station at the venue | Every minute | 45 | **03** The observation stack ## From one base unit to a network. The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol. 1. **01** Base unit A zone: cameras, counters and sensors on a GPU edge server that counts and measures density. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site A venue: every gate, concourse and stand on one server behind a security gateway, linked to the control room. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet A venue operator's grounds on one safety view. [Managed offers →](https://observatory.global/industries/events/solutions/) 4. **04** Network Venues share event records with safety authorities and emergency services. [The open protocol →](https://observatory.global/protocol/) - **01** Fixed camera - **02** Compact weather station - **03** GPU edge server - **04** Zero-trust gateway - **05** Fibre terminal - **06** Pole Radio and links ### Fibre Venues have fibre; cameras and counters reach the control room over it. Radio and links ### Private 5G A private 5G network carries temporary cameras and stewards' devices on event days. Edge computeThe server counts people in each zone from camera images without identifying anyone, compares density and flow with the safety plan's limits, warns of approaching lightning and heat, and keeps an event log. PowerVenue power with an uninterruptible supply, so the control room keeps its view through power events. **04** How it works ## From the instrument to the product. One observation's path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks. Stadiums and arenas: data path – of 07 01 Instruments Measurement with sensor identity andcalibration 02 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 03 Local network 04 Backhaul Commit with transactional outbox andpublish, delivered at least once 05 Site Consumer inbox deduplicates and applieseach record once into governed data 06 Data store Governed product through API, map orexport, correction-aware 07 Products ONVIFMQTTCAP 1.2 08 Power and structure 01 Fixed camera Ethernet 02 Compact weather station SDI-12 · RS-485 · Ethernet Turnstile and gate counters Not in the reference kit Thunderstorm warning sensor Not in the reference kit 03 GPU edge server Ethernet · Fibre · PCIe · BMC ·1PPS/10 MHz 04 Zero-trust gateway Ethernet · Fibre 05 Fibre terminal Fibre · Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Density and flow by zone Lightning and heat warnings Event logs Capacity reviews 06 Pole Ethernet · RTSP/ONVIF Ethernet · MQTT 5 Ethernet Ethernet Ethernet Fibre Fibre From the instrument to the published product: each band is a tier, each connector names its interface, and the numbers match the bill of materials. Hover or focus a block to trace its path; scroll or step to follow one observation. | Item | Equipment | Data ports | Protocols | Power in | | --- | --- | --- | --- | --- | | 01 | **Fixed camera** Fixed visible-light camera for site security, scene monitoring and machine vision. | Ethernet | RTSP with ONVIF profiles, MQTT 5 | PoE | | 02 | **Compact weather station** All-in-one or compact station for temperature, humidity, pressure, wind and rain at a site. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC | | 03 | **GPU edge server** Short-depth server with one or more accelerator modules for inference, training and AI-RAN shared compute at the edge. | EthernetFibrePCIeBMC1PPS/10 MHz | DMTF Redfish, IEEE 1588 PTP, MQTT 5 | AC mains, 48 V DC | | 04 | **Zero-trust gateway** Gateway that terminates encrypted tunnels, enforces segmentation and gates every flow by identity and policy. | EthernetFibre | — | 12 V DC, AC mains | | 05 | **Fibre terminal** Optical network terminal or media converter that lands fibre backhaul at a site. | FibreEthernet | IEEE 1588 PTP | 12 V DC, 48 V DC, AC mains | | 06 | **Pole** Utility, street or dedicated pole with clamp positions. | — | — | — | How it scales 01 Instruments Arbitrary qualified sensors and instruments whosemeasurements are ingested with calibration, units,geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, ruggedappliance, radio node, sensor gateway, satelliteterminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable localgovernance and failure domain: one or more nodesplus local network, identity, policy, evidence,storage, products and operator surfaces. SITE Node Node Node ×n 04 Cluster An optional scale or specialisation domain forscheduling, shared storage, accelerators or datalocality. CLUSTER ×n 05 Fleet Coordinates plans, acknowledgements,convergence evidence, update campaigns andcorrection propagation across nodes and sites. FLEET Fleet controller ×n 06 Federation An exchange of products, capabilities, events orwork across approved, independently administeredtrust domains, using explicit trust, policy,data-locality, version and correction contracts. TRUST DOMAIN TRUST DOMAIN TRUST DOMAIN ×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange The smallest deployable unit is one node; the same unit is replicated to meet the demand. Nodes form a site, sites may form a cluster, sites and clusters are coordinated as a fleet, and fleets exchange across independently administered trust domains. Each plane is a separate channel with its own open binding. **Data in the field**: MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses. **Telemetry**: OpenTelemetry OTLP. **Control**: TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2. **Data upstream**: At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links. **Evidence**: DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts. **Events**: Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3. **Exchange**: OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0. **05** From order to operation ## Every step, from the first call to a running site. The same crew and the same record carry the work from scope to maintenance. 1. 01 Order Scope with the safety officer The scope reads the venue's safety certificate, capacities, zones, control room and past incidents. Nexus Observatory Inc. returns the sensing design, control room integration, privacy design and a price per venue and per year. Every assumption in the scope is written down and priced. 1 2. 02 Survey Survey zones and flows Crews survey gates, concourses, stands and approaches with the safety officer: camera positions for density, counter points, weather and lightning sensor sites and network paths. Findings are recorded with drawings. Every finding is kept with the site record for the crews who follow. 2 3. 03 Permits Licensing and privacy The safety certifying authority is told of the system, privacy rules for cameras are agreed and published, and connections to the control room go through change control. Every approval is kept with the venue record. Approvals are tracked site by site, so nothing waits unseen. 4. 04 Build Build and test Cameras, counters, sensors and the server are configured with zones and limits, enrolled with their identities and tested with recorded crowds before shipping. Test results travel with the kit to the site. Nothing ships until the whole kit has passed its tests together. 5. 05 Install Install between events Crews install cameras, counters, the weather station and lightning sensor between events, connect the server behind the security gateway, and add the views to the control room. Every point is recorded. The site record is updated before the crew leaves. 6. 06 Commission Commission at a live event Each node proves its identity. Counts are compared with turnstile data and manual counts at a live event, density with stewards' reports, and lightning warnings with the regional service. Results are signed and kept with the site record. Acceptance is recorded with the owner before handover. 13 7. 07 Operate Manage the crowd Safety officers see density and flow in every zone and approaching storms. Gates are opened or held, stewards are sent to crowding before it peaks, and spectators are moved from exposed stands when lightning approaches. Reports for owners and funders come from the same record. 12 8. 08 Maintain Review every event After each event the log is reviewed with the safety team, limits and zones are adjusted, cameras cleaned and re-aimed, sensors checked and software updated in rings. Every review is kept. Spares and procedures travel with the crews. Maintenance history stays with each site for its whole life. **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Density and flow by zone** Safety officers and stewards - **Lightning and heat warnings** Event control - **Event logs** Safety certifying authorities - **Capacity reviews** Venue operators Integration - **Control room** Views and alerts join the control room systems. - **Ticketing and turnstiles** Entry counts join from turnstiles. - **Emergency services** Event logs are shared on request. Exchanged through ONVIF, MQTT, CAP 1.2. **07** Questions buyers ask ## Before you scope it. Does it identify people? No. It counts and measures density. Does it replace stewards? No. It tells stewards where to go. How early is lightning warning? As early as the thunderstorm warning system allows, with clear stages. Can temporary events use it? Yes, with temporary cameras on private 5G. **08** Resources ## The sources behind this page. Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does. 1. **1** [Guide to Safety at Sports Grounds (Green Guide), sixth edition](https://sgsa.org.uk/) Sports Grounds Safety Authority · 2018 2. **2** [HSG154: Managing crowds safely](https://www.hse.gov.uk/) Health and Safety Executive 3. **3** [IEC 62793: Protection against lightning, thunderstorm warning systems](https://webstore.iec.ch/) International Electrotechnical Commission 4. **4** [WMO-No. 8: Guide to Instruments and Methods of Observation](https://library.wmo.int/) World Meteorological Organization 5. **5** [ISO 7243: Ergonomics of the thermal environment, assessment of heat stress using the WBGT index](https://www.iso.org/) International Organization for Standardization · 2017 **09** Related ## Use cases and solutions. [Use case Stadium operations private 5G sliceA private 5G slice for venue operations beside the neutral-host network, with crowd, heat and air sensing.The full use case →](https://observatory.global/use-cases/stadium-5g/) [Solution Private Wireless as a ServiceStandalone private 5G or LTE for a site, campus, port or mine: radios, core, SIMs, spectrum route and operations.Solutions for events →](https://observatory.global/industries/events/solutions/#private-wireless) [Solution Edge inference for infrastructureModels running beside the instrument on video, radar and sensor streams for assets and hazards; only results move upstream.Solutions for events →](https://observatory.global/industries/events/solutions/#edge-inference) [Solution Sensing as a ServiceObservation networks designed, installed, operated and maintained for a monthly fee: weather, hydromet, air, seismic and environmental stations, with data delivered under a licence.Solutions for events →](https://observatory.global/industries/events/solutions/#sensing-service) **10** Events: specialized fields ## Other fields of this industry. [Specialized field Outdoor festivalsWeather, lightning, wind on structures, noise at the neighbours and connectivity for festivals, deployed for the event and taken away after.The full field →](https://observatory.global/industries/events/outdoor-festivals/) [Specialized field Marathons and endurance eventsHeat stress, air quality and weather along marathon, cycling and triathlon courses, so medical teams and race directors protect athletes and change plans in time.The full field →](https://observatory.global/industries/events/endurance-events/) [Specialized field Venue connectivityPrivate 5G and Wi-Fi at venues for broadcast, operations, payments and fans, with an edge server for video and safety, built so the network holds when the venue is full.The full field →](https://observatory.global/industries/events/venue-connectivity/) ### Bring us the site. Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details. [Plan a deployment](https://observatory.global/contact/deployment/) [Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) [Talk to sales](https://observatory.global/contact/sales-enquiry/) [Request a quote](https://observatory.global/contact/hardware-quote/) [Nexus Observatory](https://observatory.global/)**Events** . Venues that sense and connect at peak load.[Talk to us](https://observatory.global/contact/) Events - [Overview](https://observatory.global/industries/events/) - [Explainer](https://observatory.global/industries/events/explainer/) - [Specialized fields](https://observatory.global/industries/events/fields/) - [Use cases](https://observatory.global/industries/events/use-cases/) - [Solutions](https://observatory.global/industries/events/solutions/) - [Platforms](https://observatory.global/industries/events/platforms/) - [Resources](https://observatory.global/industries/events/resources/) - [Contact](https://observatory.global/industries/events/contact/) Platforms - [Observatory Protocol](https://observatory.global/protocol/) - [Protocol & Grid](https://observatory.global/grid-services/) - [Software](https://observatory.global/software/) - [Hardware & power](https://observatory.global/hardware/) - [Sensors & instruments](https://observatory.global/sensors/) - [Connectivity](https://observatory.global/connectivity/) - [Edge compute & AI](https://observatory.global/edge-ai/) - [Earth observation & GeoAI](https://observatory.global/earth-observation/) - [Space and satellite systems](https://observatory.global/space/) - [Digital twins and simulation](https://observatory.global/digital-twins/) - [Data & licensing](https://observatory.global/data-products/) - [Field services](https://observatory.global/field-services/) - [Frontier labs](https://observatory.global/labs/) Solutions - [Early warning](https://observatory.global/use-cases/street-flood/) - [Wildfire and fire weather](https://observatory.global/use-cases/wildfire-camera/) - [Environmental compliance](https://observatory.global/use-cases/methane-fenceline/) - [Asset monitoring](https://observatory.global/industries/infrastructure/) - [Private networks](https://observatory.global/connectivity/private-5g/) - [Remote power and sites](https://observatory.global/use-cases/remote-microgrid/) - [Climate and resilience](https://observatory.global/industries/climate/) - [Site twins](https://observatory.global/digital-twins/) - [Data licensing](https://observatory.global/data-products/) Industries - [Public safety](https://observatory.global/industries/public-safety/) - [Government](https://observatory.global/industries/government/) - [Cities](https://observatory.global/industries/cities/) - [Civil resilience](https://observatory.global/industries/resilience/) - [Communities](https://observatory.global/industries/communities/) - [Humanitarian](https://observatory.global/industries/humanitarian/) - [Climate](https://observatory.global/industries/climate/) - [Water](https://observatory.global/industries/water/) - [Nature](https://observatory.global/industries/nature/) - [Oceans](https://observatory.global/industries/oceans/) - [Agriculture](https://observatory.global/industries/agriculture/) - [Energy](https://observatory.global/industries/energy/) - [Telecom](https://observatory.global/industries/telecom/) - [Transport](https://observatory.global/industries/transport/) - [Infrastructure](https://observatory.global/industries/infrastructure/) - [Mining](https://observatory.global/industries/mining/) - [Industry](https://observatory.global/industries/industry/) - [Research](https://observatory.global/industries/research/) - [Education](https://observatory.global/industries/education/) - [Health](https://observatory.global/industries/health/) - [Insurance and finance](https://observatory.global/industries/insurance/) - [Events](https://observatory.global/industries/events/) Products - [Field Deployment Studio](https://observatory.global/studio/) - [Station Builder](https://observatory.global/studio/builder/) - [Field services](https://observatory.global/field-services/) - [Data products](https://observatory.global/data-products/) - [APIs and SDKs](https://observatory.global/protocol/developers/) - [Edge runtime and fleet](https://observatory.global/software/) - [Hardware catalogue](https://observatory.global/hardware/) - [Reference designs](https://observatory.global/protocol/reference-designs/) Resources - [Learn](https://observatory.global/learn/) - [Stories](https://observatory.global/stories/) - [Environments](https://observatory.global/environments/) - [Network scenes](https://observatory.global/environments/networks/) - [Observatories atlas](https://observatory.global/observatories/) - [Earth and maps](https://observatory.global/earth/) - [Technologies](https://observatory.global/technologies/) - [Countries](https://observatory.global/countries/) - [Spectrum](https://observatory.global/spectrum/) - [Specification](https://observatory.global/protocol/specification/) - [Conformance](https://observatory.global/protocol/conformance/) - [Open source](https://observatory.global/open/) - [Data credits](https://observatory.global/credits/) Company - [About](https://observatory.global/about/) - [Open governance](https://observatory.global/consortium/) - [Security and trust](https://observatory.global/security/) - [Contact sales](https://observatory.global/contact/) - [Privacy requests](https://observatory.global/privacy-request/) © 2026 Nexus Observatory Inc. [Security and trust](https://observatory.global/security/) [Privacy choices](https://observatory.global/privacy-choices/) [Accessibility](https://observatory.global/legal/accessibility/) [Privacy](https://observatory.global/legal/privacy/) [Terms](https://observatory.global/legal/terms/)