Two lines on a ticket are all anyone ever reads

A ticket, printed flat and large across the chest. Ruled into its own grid of field boxes, a perforated edge down one side, a green stamp panel in the corner. Every field carries a run of dense, illegible printed marks — except two. In a plain machine face, unmistakably clear: a day and a time. A band of the same dense marks runs along the foot, the way a real ticket ends in a printed line nobody reads at all.

The return was fixed before the visit even started, and these are the only two fields anyone was ever going to look at twice.

Why is almost everything on this ticket illegible?

Because most of what's printed on a real ticket isn't for the passenger — it's for a machine, a gate, a reconciliation system somewhere that never has a human reader in mind.

A ticket carries a fare code, a routing string, a stock number, a dozen fields that exist so a system can validate the thing later. None of that was ever meant to be read by the person holding it. Rendering those fields as dense, unreadable marks isn't a stylistic choice standing in for detail — it's what those fields actually are to the person carrying the ticket in a coat pocket.

Why leave the day and the departure time legible and nothing else?

Because those are the two facts a traveller actually holds in their head between booking the ticket and using it.

Everyone who has ever kept a ticket in a pocket for a week knows this split without being told it: you don't remember the fare code, you remember the day and roughly when you're leaving. The design just draws the line where memory already draws it — two fields promoted out of the noise, the rest left as texture.

Why does an early departure time say something on its own?

Because a 06:41 return isn't a neutral fact — it's a choice about how much of the visit's last day gets spent travelling rather than staying.

A late-afternoon departure gets a full morning out of the last day. An early one gives most of that day back to the journey home instead, which usually means it was booked around something else entirely — a working day the next morning, a connection that only runs once. The hour on the ticket is a small, specific piece of information about what the return was built around.

Does printing someone else's ticket need permission?

No — a ticket rendered with an invented day, an invented time and every other field illegible needs nobody's permission, because it doesn't reproduce a real one.

A genuine ticket carries a real operator's design, colours and marks, and those belong to whoever issued it. This one keeps the grid, the perforation and the stamp as the generic shape a ticket takes, with nothing on it that traces back to an actual service. If the point were to reproduce one specific real ticket exactly, that would be a different job with a different owner to ask.

Does this work for an outward ticket instead of a return?

Yes, though it reads differently — a single outward leg says a date was set for arriving, not for leaving, which is a different kind of commitment.

A return carries both halves of the trip in one object, and the piece is really about the second half: the leaving date decided before the visit began. An outward-only ticket, kept instead of handed over at a barrier, is closer to a case that stays packed flat on one side for the whole stay — proof of arrival rather than a record of when the arrival was always going to end.

Isn't a dated return just a booking constraint, not something worth marking?

It is a constraint, and that's exactly why it's worth marking — a date fixed weeks ahead limits a visit on both ends before either side has had a chance to say anything about how it's going.

It works both ways. It tells a host how much time they actually have, which is its own kind of consideration, not unlike holding a stretch of kerb open for somebody who hasn't even arrived yet. And it tells the visitor, on day one, exactly how many days are left before the drum's already turning by the time the clock says twelve. A ticket booked in advance takes that decision off the table entirely, for better or worse.

Does it print well?

Yes, kept to two flat inks plus the paper ground, with the grid held in a single hard black line.

The stamp panel works best as one flat block of colour rather than a gradient — a rail-ticket green reads clearly at chest size and separates cleanly from the black rule work. The illegible fields should stay coarse: short dense marks rather than anything trying to look like real characters, which would just blur into grey at fabric scale. The two legible fields carry the whole print, so keep that machine face clean and give it the most contrast on the shirt.

How do I get one made?

Describe the ticket at JustOG — which two fields stay legible, what day, what hour. Pick a direction, drag the crop frame, see it composited on the real garment, and it's made to order and shipped.

Designs other people have published are in the shop.

Two fields, a stamp, a perforated edge, and a printed band nobody was ever going to read.