Transparency
About & measurement method
Operator, clock sources, estimation method, limitations, and change history for Ticket Server Time.
Operator
The service is operated by erickim. Send measurement errors, corrections, or source updates to the email below.
- Name
- erickim
- hardline7@gmail.com
Measurement method
1. Service reference clock
The main clock synchronizes the browser with this service's application-server clock. Its millisecond digits are interpolated; it is not a certified national reference clock or a guarantee of one-millisecond accuracy.
2. Target-server estimate
The service estimates a difference from the target HTTP Date response. Since Date has one-second precision, it assumes the middle of that second (+500ms) and applies RTT/2 compensation. The conservative estimated uncertainty is at least ±(500ms + RTT/2).
The default list normally uses a ten-minute cache. RTT, measurement time, uncertainty, and failure state are shown with each value.
Limitations
- HTTP Date may represent a CDN, edge, or proxy clock rather than the origin application.
- RTT/2 assumes symmetric outbound and inbound latency.
- Browser scheduling, the device clock, and network congestion affect display and request timing.
- A clock estimate cannot predict queue entry, seat allocation, or success.
Status rules
A missing or invalid Date header is shown as "Time unavailable," not 0ms. Connection failures are offline; successful values are labeled estimates.
Change history
2026-10-01 — Separated display precision from measurement accuracy and added RTT, measurement time, uncertainty, and failure states. Course dates are published only when an official source is verified.