Live night
connecting…Night
Service
–
events ingested
–
people in zones (last 10 min)
–
spend, last hour
–
offline payments reconciled · waiting
Crowd by zone · last 10 min
Spend by zone · last hour
Running order · average Captivation
Shadow mode is off
This service is not running the Matchday feeds. Set ONDA_SHADOW=1 on the service to switch them on.
Loading…
Arrival wave · road load around the stadium
Today
Typical day, same hours
Now
Match moments
Road load is the average of the city's traffic sensors within the radius of the stadium (0 = empty, 100 = gridlock). The typical curve is the median of the same hours on earlier days without a match. Weather is observed at the stadium, hour by hour.
–
road load now
–
of nearby sensors report queues or jams
–
at the stadium now
Live sensor map
Waiting for the first sensor reading…
FluidSlow
QueuesJammed
Each dot is a road sensor at its real position; the streets show up where sensors are dense. Rings mark 500 m, 1 km and 1.5 km from the stadium. No third-party map is loaded. No person appears anywhere on this page.
Data sources
Match data: Sportmonks. Weather data by Open-Meteo.com (CC BY 4.0). Traffic: Ayuntamiento de Madrid, datos.madrid.es. Every figure here is an aggregate about a place, never about people.
Rehearsal not available
Stadium
Weather
Road traffic
Show
Seats taken
Fluid / short queueSlow
QueuesJammed / long wait
Card payments
Seats fill as fans pass the gates. Each gate shows its queue in minutes; the dots beside it are a visual cue for queue length, not individuals. Cars on the roads follow road load. Card terminals pulse with payments per minute: inside the ground and in the bars and shops around it. Hover or tap anything for its numbers.
At this moment
This scenario vs a mild, easy day
Through the match night kick-off −3 h … +2 h 30 m
Fans inside
Longest gate queue, minutes
Road load around the ground, %
Card payments per minute · solid inside, dashed around the ground
Drag or hover across any chart to move through the night. Dashed vertical line = kick-off.
Assumptions behind the simulation
Real weather and road traffic around the ground are on the Matchday tab. Real card spend is lagged by days (Mastercard GeoInsights, CaixaBank) and will come as an after-event report; the figures here only illustrate its shape.
Captivation by act
Captivation (0–100) combines time spent in front of the stage, app interactions, bar spend and merch during the set. Every figure is an average over a group; groups and histogram buckets under k people are hidden (hatched). People who objected to analytics or asked to be erased are excluded.
–
alerts this night
–
held back: no VIP-service consent
–
last alert
Alerts for the host team
An alert fires when a guest who agreed to VIP service spends above the threshold within 15 minutes in a VIP zone. The reference is a short code for the host team, not an identity. Guests without that consent never trigger an alert.
Privacy budget · this night
Released so far
Send a label message through ONDA
The label never receives contacts. ONDA delivers its message to fans who consented to that label by name, are verified adults and scored above the minimum. Preview first; sending is written to the audit trail.
Aggregate release
Consent ledger · all retained nights
Legal basis by use
| Running the event (entry, payments) | contract |
| Aggregate analytics, Captivation | legitimate interest · objection honoured |
| Personalisation, VIP service | consent |
| Messages from a named label | consent · adults only |
Consent is re-checked at the moment of every release, so a withdrawal takes effect on the next one.
–
hash chain
–
entries in the chain
–
shown for this workspace
Recent entries
Every consent, closure, release and deletion is appended to a hash-chained log that cannot be edited. Only non-personal fields are shown here.