Ticket scanning system for Club Atlético Tigre stadium
An app for the handheld readers used at the stadium gates, plus a web panel to follow admissions live. With a full house, up to 40,000 people come in over roughly two hours through four gates, and it all has to keep working even when the connection drops.

Scans and decides on the spot
The operator points the reader at the ticket code or the ID, and in under half a second the screen says whether the person goes through. No waiting on a server.
Works without internet
Every device holds the ticket list inside it. If the stadium WiFi drops — and it does — people keep coming in. When signal returns, everything scanned uploads on its own.
Green, yellow or red
Green goes through. Yellow means the ticket is valid but belongs at another gate, and shows which one. Red doesn't pass, and says why: already used, cancelled, or not on the list.
Each ticket works once
Once someone is in, their ticket is spent and no other device will take it again. That's what stops the same ticket from letting in two people.
Easy to use at the gate
Big buttons, big text, and no username or password. Staff rotate, work standing up and wear gloves: they have to be able to pick up the device and go.
The supervisor sees it live
From a computer you can see how many people came in per section, how each gate is doing, and whether any device stopped responding.
Try the gate reader
This is the actual app running, with the same rules used at the stadium. Tap a ticket from the queue to scan it and see what the operator gets back. You can also change which gate the device is standing at, or leave it without signal.

Tickets in the queue
Tap one to scan it, or use ESCANEAR on the device to take the next one.
Device configuration
Note: The app is internal to the club and ships in Spanish only, so the device screen doesn't follow the site language.
The supervisor's panel
What you see from the computer while the crowd comes in. It refreshes on its own every 3 seconds.
62.480 reads received
3 devices are reading in perimeter mode
Gate 4, Gate 7 and Lateral 2. In perimeter the ticket is validated but not consumed, so those people don't count under "Entered through a gate". If they need to burn, switch them to gate mode.
How admissions spread out
How many people came in during each 15-minute window. The peak lands right before kick-off.
By sector
| Sector | In | Total | Progress |
|---|---|---|---|
| 66 Popular Cabecera | 9.186 | 12.400 | 74% |
| 67 Popular Lateral | 6.402 | 9.850 | 65% |
| 68 Popular Visitante | 1.827 | 2.100 | 87% |
| 69 Platea Sector A | 892 | 1.640 | 54% |
| 70 Platea Sector B | 845 | 1.580 | 53% |
| 73 Platea Sector E | 703 | 1.420 | 50% |
| 74 Platea Sector Preferencial | 641 | 980 | 65% |
Devices
A device that hasn't reported in over a minute may be a gate that went down.
| Device | Mode | Reads | Status |
|---|---|---|---|
Puerta 1 M. Acosta · 66 · Popular Cabecera | GATE | 3.412 | ONLINE heartbeat just now · uploaded just now |
Puerta 2 J. Ledesma · 66 · Popular Cabecera | GATE | 3.188 | ONLINE heartbeat just now · uploaded hace 1 min |
Puerta 4 S. Ojeda · 67 · Popular Lateral | PERIM | 2.744 | NOT SEEN heartbeat hace 1 min · uploaded hace 1 min |
Puerta 5 R. Britos · 67 · Popular Lateral | GATE | 2.960 | ONLINE heartbeat just now · uploaded just now |
Puerta 7 L. Ferrari · 68 · Popular Visitante | PERIM | 1.827 | NOT SEEN heartbeat hace 2 min · uploaded hace 14 min |
Platea A C. Roldán · 69 · Platea Sector A | GATE | 1.704 | ONLINE heartbeat just now · uploaded just now |
Platea B N. Vera · 70 · Platea Sector B | GATE | 1.538 | ONLINE heartbeat just now · uploaded hace 2 min |
Lateral 2 F. Duarte · Todos | PERIM | 986 | NOT SEEN heartbeat hace 4 min · uploaded hace 4 min |
Tech stack
Running a similar operation?
Systems that have to work without a network, at scale, with people waiting. Tell us about yours.
Let's talk