A timestamp printed on a page, and its missing offset

Session and account

A printed timestamp is a moment written as text, and the text is either complete, ambiguous, or missing the single field that gives it meaning.

The shape

There is one written form that cannot be misread and several that can. The unambiguous one puts the largest unit first and finishes with an explicit statement of how the clock relates to a common reference. Everything else is a local convention that happens to be legible to the people who share it.

Order: largest unit first: year, then month, then day, then hour, minute, second
Date part: four digits, a hyphen, two digits, a hyphen, two digits. The two digit fields are padded, so the fourth day of a month is written with a leading zero
Joiner: the letter T, or a single space. Both are common and neither creates ambiguity
Time part: two digits, a colon, two digits, a colon, two digits, on a twenty four hour clock
Offset: either the letter Z, or a sign followed by two digits, a colon and two more digits
Total width: twenty characters with a Z ending, twenty five with a numeric offset

the skeleton: four digits, dash, two, dash, two, T,
two, colon, two, colon, two, then the offset field
####-##-##T##:##:##Z
####-##-##T##:##:##+##:##

the same moment, three ways, one of them incomplete
2026-01-02T03:04:05Z
2026-01-02 03:04:05+00:00
2026-01-02 03:04:05           <- offset missing

The date shown carries no meaning; it was chosen so every field is short and countable.

The offset is the part that goes missing

Of everything that can be wrong with a written time, the absent offset is the most common and the most costly. A time with no offset is not a moment. It is a reading from a clock whose relationship to every other clock is unstated, and no amount of care in the rest of the string repairs that.

It is costly because it fails quietly. The string looks complete. It has a date, it has hours, minutes and seconds, and it will be read by most people without a second thought. The information it is missing is information they will supply themselves, from the assumption that it must be their own clock, and that assumption is wrong roughly as often as it is right.

The letter Z at the end is the compact way of stating an offset of zero. A numeric offset states the difference explicitly. Either is complete. Nothing is complete.

The ambiguous forms

Two conventions collide constantly. Written as three numbers separated by slashes, a date can mean two different days depending on which convention the writer used, and there is no way to tell from the string when both numbers are twelve or under. A date written as 03/04/2026 is the third of April to one reader and the fourth of March to another, and both readings are confident.

The twelve hour clock is the second source of trouble. Without the trailing marker, an hour between one and twelve is two possible times. With the marker but written by hand, the marker is the first thing lost when a string is trimmed or reflowed.

The two digit year is a third. It is rarer than it was, and when it appears it converts a date into a guess about a century.

How to check it by eye

Reading a printed time backwards

Read the last character first. If it is a digit and there was no sign earlier in the time part, the offset is missing and the string is a local reading of an unnamed clock.
Count the leading field. Four digits means a year and the order runs from largest to smallest. Two digits means you cannot be certain what the first field is.
Look for a slash. Any date built with slashes has a convention problem waiting in it unless one of the numbers is over twelve.
Check the hour against twenty four. An hour of thirteen or more settles the clock convention on its own; an hour under thirteen settles nothing.

What a wrong shape means

Malformed times are usually the residue of formatting rather than of anything sinister. A date rendered by one system and reformatted by another, a spreadsheet that reinterpreted a text column, a template that printed a placeholder because a value was absent, a string trimmed to fit a column width.

A time in an impossible position deserves a different reading. Thirty two days in a month, an hour of twenty five, sixty one seconds where no leap is involved: these are arithmetic faults, and they mean a value was assembled rather than formatted from an actual moment.

None of this constitutes evidence about intent. The honest conclusion from a broken time is that the pipeline that printed it is imperfect, which is true of nearly every pipeline.

What a correct shape does not prove

A time is a claim. Whoever rendered the page chose what to print, and formatting rigour is not evidence of accuracy. A perfectly formed string with an explicit offset can still be wrong in every way that matters.

Not that the moment described ever happened. The string is text and text can be typed.
Not that the clock that produced it was correct. A well formatted reading from a drifting clock is still a well formatted string.
Not that it refers to what the surrounding words say it refers to. The label beside a time is prose, and prose is not constrained by format.
Not that it was generated when the page was rendered rather than copied from somewhere older.
Not that the offset stated is the offset that applied. The field is written by the same process that wrote the digits.

What this card is not

Calendars, leap seconds, zone rules and the history of local time changes are outside this reference and would not fit its purpose. This card also publishes no time of its own and treats no printed time as a status: this site measures nothing and does not record when anything was last seen. The machine written form of the same information is covered at a time written as a plain integer.

A timestamp printed on a page