Keeping a Sighting Logbook: From Scraps of Paper to a Real Database

Updated: August 2026 – A sighting logbook is the point at which casual observation turns into a real collection. This guide shows you which fields you actually need, how to migrate paper and spreadsheet records without losing data, and how to structure your logbook so it produces statistics later – instead of just being one long wall of text.

What is a sighting logbook – and what isn’t it?

A sighting logbook is a structured collection of individual observations, in which every sighting fills out the same fields. That’s exactly what distinguishes it from a spotting diary: a diary tells the story of a day, a logbook records events in a comparable form. Only the second version can later be searched, filtered and analysed.

In practice that means a single hard rule: one entry equals one observation. If you see the same vehicle in the morning and again in the evening, that’s two entries – otherwise you can never say later how often you actually encountered a particular class. Anyone who just jots down “lots of activity today” doesn’t have a logbook, they have a memory.

The data model: which fields you really need

The temptation is great to set up twenty fields from the start. In practice you never fill them all in, and half-empty columns wreck your analysis. So start with a lean core and only add what you’ve missed twice.

Field	Required	Example content	What you’ll need it for later
Date	yes	2026-08-19	Time series, seasonal comparison, annual statistics
Time	yes	14:32	Daily patterns, rotation reconstruction
Place	yes	Main station, north platform	Hit rate per spot, map analysis
Vehicle	yes	Class or carriage number	Coverage of your collection, vehicle history
Direction	yes	Heading south	Assignment to lines and routes
Source	yes	Seen myself / community	Separating your own data from others’
Note	no	Special livery, diversion	Context, memory aid, search terms
Certainty	no	Certain / uncertain	Filter for reliable analysis
Photo reference	no	File name or link	Evidence, verifiability

The decisive discipline isn’t the number of fields, but consistent spelling. If the same station is sometimes called “Hbf”, sometimes “main station” and sometimes “HBF North”, every statistic falls apart into three piles. So set yourself a fixed list for places and vehicle names and use only that. With brands, there’s the added twist that they outlive operator changes: the 3-Länderbahn brand around Siegen keeps its name even though a different company runs it today. How strongly standardisation pays off can also be seen in well-grown sighting archives, such as in the guide to pictures and sightings on Drehscheibe Online.

Why the “source” field matters so much

Almost every spotter picks up third-party information at some point: a tip from a group, a report from a forum, a photo from a friend. That’s entirely fine – but only if it stays separated. Otherwise your statistics will eventually claim you saw vehicles you never actually laid eyes on. A single field with three possible values solves the problem permanently. How to correctly read and assess other people’s reports is shown in the guide to live sightings in real time.

Paper, spreadsheet or app – which level suits you?

All three variants use the same data model; they only differ in convenience and how easy they are to analyse.

Criterion	Paper	Spreadsheet	Spotting app
Logging on the go	very fast	cumbersome	fast, with pre-filled fields
Timestamp	manual	manual	automatic
Consistent spelling	down to discipline	down to discipline	via dropdown fields
Search	not possible	limited	direct
Analysis	manual work	with formulas	built in
Backup	photos of the pages	file copy	export and backup
Failure risk	loss, water damage	file corruption	changing devices

Paper has an underrated advantage: it always works, even with a dead battery and in the cold. At a spot like Abisko on the Malmbanan, that’s not a minor point, it’s the basic requirement. Many experienced spotters therefore work in two stages – quickly on paper outdoors, cleanly into the digital structure in the evening. Anyone making the full switch will find the criteria that matter in the overview of the trainspotting app with a sighting feature. Additional comparison points are provided by the comparison of the best trainspotting apps.

Is your logbook ready for analysis?

Migrating old records without losing data

Switching over from paper or a spreadsheet that’s grown over time is the moment when most collections take damage. Not because data is missing, but because things get “tidied up” during the transfer. So stick to a clear sequence.

For historical research on older vehicles, it’s worth checking image archives while migrating, such as the one described in the article on Eisenbahnarchiv.de with historical railway photos. That often lets you retroactively pin down unclear type details without guessing. It also helps to think in terms of platforms rather than manufacturer names – since the takeover of Bombardier Transportation, much of it comes from Alstom, though that’s rarely visible on the vehicle itself.

What a clean logbook produces

Once the structure is in place, analysis almost happens on its own. The same fields can answer very different questions:

• Hit rate per spot: how many sightings does an hour at a particular location bring? This lets you prioritise your time – that Cologne main station tops the list with over 1,200 train movements a day is hardly surprising; the ranking below it is far more interesting.
• Collection coverage: which classes are you still missing, even though they run in your region? That automatically produces a target list.
• Seasonal patterns: when do unusual workings occur more often? Special traffic often follows recurring rhythms.
• Daily pattern: at what time of day have you been most successful so far? Often it’s not the time you’d instinctively guess.
• Vehicle histories: how often, and where, have you encountered a particular vehicle? Over the years, this builds a surprisingly dense picture.

An often underrated side effect concerns memory. Anyone collecting over years shifts observations around in their head: vehicles drift into the wrong years, places get mixed up, frequencies get dramatically overestimated. A logbook is therefore not just an analysis tool, but also a correction to your own memory – and it regularly surprises. Almost every spotter believes they’ve seen a particular class “constantly”, then finds just five entries across three years.

If you enjoy the playful side, you’ll quickly notice: points and badges are nothing more than ready-made analyses built on exactly these fields, as shown in the overview of the trainspotter game with points and badges. And if you also want to tag your photos properly, the workflow section of the guide to bahnbilder.de with upload and tags will help.

Common mistakes with a sighting logbook

• Too many fields too soon. Twenty columns with only five filled in are worse than seven complete ones. Only expand once you’ve missed something twice.
• Combined lines instead of individual entries. “Saw three double-deck trains today” can never be resolved back into time and place.
• Free text for places and vehicles. The most common reason collections become unusable after two years.
• Mixing your own and other people’s sightings. Without a source field, nobody will later know what you actually observed yourself.
• Retroactively tidying up. Anyone who “completes” unclear details while digitising creates data that never existed. That also applies to operators that no longer exist in that form: an old entry for Abellio stays correct and only becomes wrong through rewriting.
• No backup. A logbook that only lives on one device is a logbook on borrowed time. One export per quarter is enough.
• Separating equipment and notes. If you never have a pen on you, you’ll never note anything down. What belongs in your bag is listed in the trainspotting equipment overview.

Conclusion

A sighting logbook isn’t busywork, it’s an investment in your own collection. What matters isn’t as many fields as possible, but a few consistently filled ones – and uniform spellings that still fit together after years. Anyone who doesn’t correct anything while migrating and lets uncertain things stay uncertain keeps an honest dataset. From that point on, the rest more or less takes care of itself: statistics, targets and gap lists appear as a by-product.