Reporting a Sighting: How Your Observation Becomes a Good Report

Updated: August 2026 – You want to report a sighting, but aren’t sure what actually needs to go in it? This guide shows you the practical standard: the four details every report needs, how to describe place and direction unambiguously, and the typical mistakes that make a report worthless to everyone else. Includes good vs bad examples for direct comparison.

What belongs in a sighting report?

A complete sighting report consists of four required details: time, place, vehicle and direction of travel. Miss one of these, and nobody else can do anything with the report – it becomes a purely personal note. Everything beyond that – route, livery, formation, occasion or a photo – is a valuable extra, but it never replaces any of the four basic details.

The test is simple: can a stranger who doesn’t know your region tell from your report whether it’s worth heading out? If yes, the report is good. If they’d have to ask a follow-up question, something’s missing. You can see how strongly this principle shapes the quality of entire platforms in the overview of live sightings in real time.

The four required details in detail

Time: accurate to the minute, not by feel

The most common mistake in sighting reports isn’t the wrong vehicle number, but a vague time. “Just seen” is correct the moment you write it – and already useless ten minutes later, because nobody knows when “just” was.

Always write down the actual observation time, not the time you’re posting. If you only get round to it in the evening, that’s not a problem, as long as you make it clear: “seen at 14:32, only reporting now” is a clean report. For scheduled services, it also helps to include the train number – how to decode it is explained in the guide to decoding train numbers for ICE, IC, RE and RB.

Place: a reference point others can find

The place needs to be described so that someone can find it again on a map. Three building blocks achieve that:

• A fixed reference point: a station, stop, bridge, road junction or another point with an official name.
• Refinement: platform, side of the track, compass direction, or “north of the bridge”.
• Direction you were facing: the perspective you observed from – this also makes photo reports easier to verify.

Plain town names are too vague. Plain coordinates are precise but impractical for most readers, since they first have to be copied and looked up. The combination of a name plus a rough location is the standard that both forums and apps work with – including in the classic sighting threads, as shown in the guide to pictures and sightings on Drehscheibe Online.

Vehicle: as precise as you can be sure of

For the vehicle, there’s a hierarchy of precision, from most to least specific:

1. A specific vehicle number (carriage, operating or UIC number), if read with certainty
2. Class or vehicle type without an individual number
3. Vehicle family or design, e.g. “four-car electric multiple unit”
4. A distinctive feature, e.g. a special livery or advertising wrap

Always report the highest level you’re certain of – and the next one down as an honest limitation. “Advertising-liveried loco, number not readable” is a good report. A guessed number, on the other hand, is the fastest way to ruin your standing in the community. The same applies to the operator: the trains in North Rhine-Westphalia carry National Express branding, behind which stands the Mobico Group – if you’re unsure, report the name shown on the vehicle, not the company you assume it to be.

Direction of travel: more important than the starting point

For anyone who wants to use your report, one piece of information matters most: where is the vehicle heading next? Only that lets people plan ahead. So state the direction – either as a destination, a route direction, or, failing that, a compass direction. If the vehicle was stationary, say so just as clearly, because a stabled set is a completely different piece of information from a moving one.

Good or bad? Reports compared directly

The table below sets typical phrasings side by side. It shows that the difference is rarely about length, but about clarity.

Detail	Weak report	Usable report	Why it makes the difference
Time	“just now”	“14:32”	Only with a time can you judge whether it’s still worth heading out
Place	“seen in town”	“main station, north platform”	Someone unfamiliar with the area can find the spot without asking
Vehicle	“some old train”	“older loco-hauled train, loco number not readable”	An honest gap beats a vague claim
Direction	“was on its way”	“departed heading south”	Only the direction allows someone to plan their own trip
Safety	“stood right at the track”	“observed from the platform”	Reports shouldn’t normalise risky behaviour
Context	“insanely rare!”	“transfer run, unusual for this line”	Context helps others understand the value of the sighting

Are you ready for a clean report?

How to go about reporting

The process is always the same – whether you’re on the platform, at the stop, or at a photo spot.

Anyone out regularly develops a routine of under a minute from this. The side effect: your own reports become a searchable archive that lets you spot patterns – much like spotters who consistently collect their observations in a trainspotting app with a sighting feature.

When is a sighting “live” – and when is it archive?

Live sightings and reports made after the fact serve different purposes, and both have their place. What matters is that you make clear which kind you’re currently providing.

• Live report: made directly after the observation, so others can still react. For urban services, that window is often only a few minutes wide; for special workings and transfer runs it’s considerably longer.
• Delayed report: made some hours or days later. It no longer helps anyone head out, but is very useful for reconstructing rotations and usage patterns.
• Archive entry: an older observation added retrospectively. It’s valuable for statistics and vehicle histories and should be clearly marked as old.

The mistake to avoid is mixing the two: a three-day-old sighting that looks like a live report sends people out for nothing. Where live data actually comes from in practice, and how quickly it ages, is covered by the guide to live train tracking and Zugradar.

Common mistakes when reporting a sighting

• Leaving out the time. By far the most common mistake. Without a time, every other detail is worth only half as much.
• Guessing numbers. A made-up digit looks like precision, but leads to false vehicle histories. Write “not readable” instead.
• Only naming the town. Anyone who doesn’t narrow down the location forces every reader to ask a follow-up question – and most simply won’t bother.
• Forgetting the direction. Without a direction of travel, nobody can plan. That’s especially true for special workings, as shown in the guide to finding special trains and charter runs.
• Including risky behaviour. Location descriptions that suggest closeness to the track or railway property have no place in a report – not even as an anecdote.
• Posting people and number plates unfiltered. Vehicles are the subject, people are not. What to watch out for legally is covered in the guide Are you allowed to photograph trains?
• Cramming everything into a single sentence. Four clearly separated details are quicker to take in than one convoluted sentence.

What good reports achieve in the long run

A single sighting is one data point. Hundreds of clean sightings form a picture: which vehicles regularly run where, which rotations are stable, which class is currently disappearing from everyday service. That’s exactly why active spotters value consistency of format – not out of pedantry, but because only uniform data can be analysed later.

There’s also a social effect: anyone who reports reliably is quickly seen as a trusted source in the trainspotting community. Conversely, sloppy reporting spreads just as fast. And if you enjoy the playful side of it, consistent reports also feed into points and badges, as described in the overview of the trainspotter game with points and badges.

Conclusion

A good sighting report isn’t an essay, but a four-field form in your head: when, where, what, where to. Anyone who consistently delivers these four details and flags what’s uncertain as uncertain produces reports that others can act on immediately – while building an archive along the way that grows more valuable with every entry. The difference between a useless report and a strong one doesn’t cost you any extra time, just a bit of discipline while typing.