My notation method since a year or so ago is Google Keep - it's fairly quick to dig out and can be pulled up directly from a PC later to save you having to read through it all on the phone screen. Partly to initially disguise what I was documenting, I used a code to write down the unit numbers, rather than the whole numbers themselves. In practice, it works out quicker for LUL stock, but longer-winded for proper national stock, but having got used to it, it's second nature to write now - as an example if I travel on 2009TS car 11024, I consider that train 12 of the set, so simply record V12.
The letter I used for the 92TS on the central line since that was being discussed is E (as C was used for C stock), so if travelling on 92213 that would be E213.
Coding each class on the national network was a bit more complex though, I ended up doing it alphanumerically - i.e. substituting letters for numbers, such as for 321336 it would be CUC36.
Since I ended up recording my journeys the same way, my note files can look quite messy!
e.g.
CUC36 1745LST SOV A1808SNF
The underground complicated matters further without having a published timetable, so rather than used the timetabled departure, I used actual departure time, and the destinations of the trains around it so I could, if I wanted, gather what service it was by looking at the journey planner. Here's an example from thursday:
1729 SC40 1733ZFD (M30/31, CM +2/4) A1756WEH
SC would denote an S7 - the original idea being the C denoted it would replace a C stock, but in the end I just used SC for all S7s, since with a combined fleet you can't really tell some of the time.
I wouldn't feel too bad about having a small list of 377s - I have a mere 32 to my name at the moment, across all the subclasses!
), although I have no idea when I'll next be in London, not until the end of July at the earliest. For a proper full day, that's not going to be for a while unfortunately.
Just finding a day when I can do it all!
). Shame the 66 was dud.
