Reading a Sightings Heatmap: Where Things Are Actually Running

Updated: August 2026 – At first glance, a sightings heatmap looks like a map of train traffic – but it’s really a map of spotters first. Anyone who doesn’t know this difference plans trips to places that only glow red because they’re well connected and well known. This guide shows you how to read sighting data correctly, correct for distortions, and turn it into robust tour planning.

What does a sightings heatmap actually show?

A sightings heatmap shows the density of reported observations, not the density of train traffic. Red areas initially mean just one thing: many people have logged something there. Whether that’s down to high traffic volume, good accessibility, a location’s popularity, or simply an active local scene isn’t captured by the colour.

This distinction is the whole crux of the analysis. Sighting data is so-called opportunistic data: it arises wherever observers happen to be, not according to a sampling plan. That’s exactly why it needs a few correction steps before drawing conclusions – and exactly why it’s still valuable, because it captures things no official data stream records. What sightings deliver day to day is covered in the guide to live sightings in real time.

The three big distortions

Before you interpret a map, you should know which effects you’re seeing that have nothing to do with traffic.

Distortion 1: spotter density

Where many spotters live, there are many reports. Urban areas therefore almost always appear hotter than rural regions – even where more freight traffic rolls through the countryside. A comparison of two locations is only fair if both have a similarly sized scene nearby.

Distortion 2: accessibility

A platform with a roof, a bench and a connection to local transport collects sightings. A bridge that’s a 40-minute walk away collects hardly any – regardless of how much runs there. Accessibility is therefore the second-strongest driver of the map’s colour. Which locations are classically overrepresented is shown in the overview of the best stations for trainspotting.

Distortion 3: time of day and day of the week

Sightings pile up where people have time: in the afternoon, at weekends, during holidays. Early morning is underrepresented in almost all community data – even though it’s often traffic-wise the most interesting window. Anyone only looking at the overall map systematically misses these time windows.

How to normalise sighting data

Normalising means introducing a reference figure so numbers become comparable. Four approaches work for sighting data.

Approach	What you calculate	What it’s good for	Effort
Sightings per hour	entries divided by observation time	comparing locations, choosing time windows	Low, if times are recorded
Sightings per reporter	entries divided by number of people	factoring out spotter density	Medium
Share of rare vehicles	notable sightings divided by all	judging quality over quantity	Medium
Distribution across hours of the day	entries per hour for one location	finding the best time of day	Low
Comparison of similar locations	only comparable places against each other	quick practical comparison without maths	Very low

The last approach is the most pragmatic: compare a main station with a main station, and a rural platform with a rural platform, not across all types at once. That sidesteps most distortions without using a single formula.

Work out your hit rate

Which analysis suits your goal?

From analysis to tour planning

Data is only worth something once it changes a decision. This order has proven itself.

For structural cross-checking, it’s worth reading the guide to reading railway line maps with KBS numbers and operating points; for the mapping work itself, the overview of the trainspotter map with hotspots and planning.

What sighting data can do that official data can’t

The real value of community data lies not in the volume, but in what it captures at all.

• Vehicle detail. Official real-time data knows journeys, not vehicles. Which locomotive worked a service is recorded exclusively in observations.
• Freight traffic. Practically invisible in passenger information systems – but very much present in sighting data, as the guide to tracking freight trains describes.
• Special workings and transfer runs. They rarely appear in timetable data, but regularly in reports; how to find them is shown in the guide to special trains and special workings.
• Diversions. When a route isn’t stored in the system, technical displays fail – a sighting, on the other hand, always works.
• History. Forums and photo collections document years back, as the guide to photos and sightings on Drehscheibe Online shows.

Conversely, for the question “when’s the next train coming”, official data is unbeatable. The two sources don’t compete, they complement each other.

Your own data: the most robust foundation

Community maps are a good starting point, but have one drawback you can never fully fix: you don’t know the conditions of other people’s observations. With your own data you know everything – which is why it’s more valuable for planning, even though it’s much smaller.

What to record per sighting. Place, time, vehicle and direction of travel are the minimum. Anyone who also notes observation duration can normalise later – the decisive step for comparing two locations fairly. Weather and light conditions are also worth recording, because they explain why a session went well or badly.

Why zero-sighting entries count too. Most people only document the highlights. That creates the same distortion as on the big map, just on a small scale: you remember the productive hours and forget the empty ones. Anyone who notes that a location delivered nothing for two hours on a Tuesday morning has gathered information just as valuable as a rare sighting.

When an analysis starts to hold up. For a rough statement about the best time of day at a location, you need several visits at different times of day – a single good afternoon is chance, not a pattern. Experience shows statements only become stable once you’ve visited the same point over several weeks at various times.

What follows from this. After a few months you can answer questions no general map can: which of your locations is worth the early shift? Which days of the week are more productive for you? Where do unusual vehicles turn up? These answers are tailored to your region and your access – and therefore practically always more useful than a nationwide average.

Common mistakes in analysis

• Reading red areas as traffic density. They’re first observer density. Confuse the two and you’ll keep heading to the same stations.
• Comparing absolute numbers. Without reference to observation time or number of reporters, two locations aren’t comparable.
• Writing off cold zones. Missing reports are a statement about the scene, not about the traffic.
• Only using weekend data. Weekday traffic looks completely different – and is often more productive.
• Filtering out outliers. It’s precisely the individual reports away from the clusters that contain the most interesting information.
• Heading to a location without checking access. No data point justifies entering track areas or operational installations. How to assess locations properly, photographically and legally, is described in the guide to railway photography with tips and locations.

Conclusion

A sightings heatmap is a powerful tool – but only if you read it for what it is: a map of observation. Once you factor in spotter density, accessibility and time of day as distortions and normalise against a reference figure, a pretty patch of colour becomes a planning foundation. The person who gets the most out of it doesn’t just read the map, but logs their own entries too – including the quiet hours nobody else reports.