Free interval tool
Telegram delivery clock calculator
Four declared UTC clocks and one declared validity boundary. No clocks or prices are fetched.
Four events, not one verified latency
The calculation subtracts source from relay, display and quote observations. Inputs must use full UTC dates and represent the same originating family. Equal clocks are permitted. The required order is source, relay, display, quote; negative or out-of-order legs are rejected rather than silently rounded into a favourable interval.
The arithmetic assumes your declared clock basis. It cannot establish synchronisation, source authenticity, device observation precision or quote executability. If a clock is unavailable, the corresponding real evidence claim remains unknown. Do not enter a guessed timestamp just to make this classroom worksheet produce a number.
Completed fictional midnight case
Source is 12 October 2026 at 23:59:50 UTC. Relay is 23:59:55, display is 13 October at 00:00:20 and quote observation is 00:00:35. The resulting intervals are five, thirty and forty-five seconds. Full dates keep the midnight transition explicit.
With a declared forty-second expiry, the quote observation is outside the supplied rule. Equality is treated as within this classroom boundary. That comparison does not establish an account fill, reject an actual order or assign a loss. A different real publisher rule needs its own exact definition.
Export the assumptions with the result
The downloadable case retains the event inputs, intervals and validity conclusion. It is declared-input arithmetic, not a delivery certificate. Editing any input invalidates the prior result. Calendar dates and time components are checked so a date that silently rolls into another month is not accepted as an exact clock.
No messages, account keys or private files are needed. Browser-page reset does not change a messaging subscription. A real source-to-account assessment still needs original event records, matching message families, actual operation states and the clock uncertainty. Search and hosting requests have separate handling described on the privacy page.
Read precision beside the interval
Two entered second-level clocks can produce an exact subtraction while the source records themselves are approximate. If an observed source is only precise to a minute, retain that uncertainty in the external evidence packet. The calculator does not create better timestamp precision or confirm that the four events belong to the same source family.
An invented source-to-display interval of thirty seconds and a source-to-quote interval of forty-five seconds describe different endpoints. Reporting only the earlier endpoint as the time of action hides the extra observation leg. Keep both, then compare the actual quoted instruction with its declared boundary. A displayed quote can still be unavailable for the desired quantity, and no executable-price guarantee is made.