7d 30d 90d all data through 21 Jul 2026 3:35 PM

The Mummy and coffin of Pausiris

5 groups joined · 0 served
Time in exhibit · serve → complete · n=0
average
median
P95
P99
Time in queue · join → summon · n=5
average
6s
median
6s
P95
9s
P99
9s
Summon → arrival · summon → serve · n=0
average
median
P95
P99

Confessional

1 groups joined · 1 served
Time in exhibit · serve → complete · n=1
average
4m 43s
median
4m 43s
P95
4m 43s
P99
4m 43s
Time in queue · join → summon · n=1
average
3s
median
3s
P95
3s
P99
3s
Summon → arrival · summon → serve · n=1
average
14s
median
14s
P95
14s
P99
14s
Glossary — every term on this page

Tags: MEASURED = real observation · DERIVED = computed with an assumption or definitional choice · ASSUMPTION = timer/estimate, not observed · SELF-REPORTED = visitor-entered · CONFIG = a setting · DISPLAY = cosmetic threshold.  Full glossary →

Data sources

State transition log MEASURED
Every state change of every queue entry (join, summon, serve, …) with a server timestamp. The backbone of every number on this dashboard.
Location pings MEASURED
Device reports: which named venue spaces the device is in, battery level, timestamp. Cadence is device-driven — gaps of minutes are normal, and a dead or offline device simply stops pinging, so any 'location' is only as fresh as the last ping.
Group size SELF-REPORTED
Declared by the visitor when joining the queue. Every people-count on the dashboard scales by it.
Queue configuration CONFIG
Capacity, estimated view time, summon expiry windows, open/close times — settings, not observations.

Per-visit anchor timestamps

joined_at MEASURED
The Join Queue transition.
summoned_at MEASURED
The last Summon / Force Summon before the serve — the one the visitor actually acted on, so postpone-and-resummon cycles don't distort the walk time. For never-served groups, the first summon.
served_at MEASURED
The Serve transition — the staff button-press, used as a proxy for arrival.
completed_at ASSUMPTION
The Complete transition, fired by a timer ≈ the configured estimated view time after the serve.

Intervals, statistics & sync

Interval (from / to, presets) DERIVED
Whole Hobart days, inclusive. A visit belongs to the interval if its join falls inside it. Default: the 30 days ending on the latest event in the database.
data through … MEASURED
The newest transition synced into the local stats database (the sync watermark). The ↻ refresh button pulls anything newer from the source.
average / median / P95 / P99 DERIVED
Mean and interpolated percentiles over the per-group durations in the interval. P95 = 95% of groups were at or below this value; P99 shows the worst-case tail.
n= MEASURED
How many groups had both endpoints of that metric recorded — the sample the statistics are computed over.

Exhibit metrics

groups joined / served MEASURED
Entries whose join falls in the interval; “served” is the subset that reached Serve.
Time in queue (join → summon) DERIVED
summoned_at − joined_at (for the rare direct serves, served_at − joined_at). Includes groups that were summoned but never arrived. A visitor who postpones inflates their own queue time — the delay was their choice.
Summon → arrival (summon → serve) DERIVED
served_at − summoned_at, only where both exist. Serve is the staff button-press, so this includes staff reaction time, and groups that never arrived are excluded — it only describes successful arrivals.
Time in exhibit (serve → complete) ASSUMPTION
completed_at − served_at. Complete is timer-fired at ≈ the configured view time + ~5 s, so this metric essentially echoes configuration (Breathe median 8m 25s vs 500 s configured; Confessional 3m 05s vs 180 s). It is not a measurement of how long people really stayed — true dwell would have to come from location pings.