Open an event and look below Sales on its overview. Admission & arrivals shows when tickets were checked in, how many admissions are still outstanding and the busiest part of the evening. The report remains available after the event, so you can review arrival patterns when planning the next one.

Example using demo data: 417 of 1,000 admissions checked in at 22:30. The busiest 15-minute interval contains 57 arrivals.
Example using demo data: 417 of 1,000 admissions checked in at 22:30. The busiest 15-minute interval contains 57 arrivals.

Read the report

  • Redemption rate: recorded check-ins divided by recorded check-ins plus valid unused admissions.
  • Checked in: one count per individual admission. Group tickets count their members separately; guest-list admissions are included.
  • Not yet checked in: valid admissions that have not been redeemed. Cancelled, refunded and otherwise invalid unused admissions are excluded.
  • Busiest interval: the largest number of check-ins in one interval. Ties show the earliest interval.

The graph normally uses 15-minute intervals, including intervals with no arrivals. Long reporting ranges use wider intervals, with at most 192 points. The current interval can still be incomplete. Labels use the venue timezone; tooltips include UTC offsets so repeated hours during a clock change stay distinguishable.

When it appears and updates

The report appears from the local calendar day of doors opening, or the event start when no door time is set. A red LIVE tag appears from doors opening until the scheduled event end. The visible page refreshes the report every 30 seconds on the event day and for six hours after the end. Hidden tabs catch up when opened again; older reports refresh when you revisit the page.

What the numbers mean

Accepted offline scans are placed at their original scan time when they reach Usetix. Other check-ins use the recorded redemption time. A scanner clock ahead of its synchronization time falls back to that recorded time. Repeated or rejected scans do not create another arrival. An arrival that already happened stays in the history after a refund or order archival.

Use the curve to see when your door team was busiest and compare it with earlier evenings when scheduling staff. These are recorded ticket admissions, not a measurement of people currently inside. Unscanned guests will be missing. The report does not predict future arrivals.

Access and integrations

Owners and managers can read their account’s reports. External co-organizers can read reports for currently assigned events. Promoters have no access to this report.

The Admin API, built-in assistant and MCP use the same report. Ask “When did guests arrive at Club Night?” or call event_arrivals with event_title. The read-only MCP tool needs usetix:read. API requests require a read or write token. Times in the machine-readable response are UTC, accompanied by the venue timezone.

usetix events arrivals club-night
usetix events arrivals club-night --intervals
usetix events arrivals club-night --json

The CLI reads the report once per command. --intervals adds the timeline to human-readable output; --json always includes it. --count prints checked-in admissions.