DynamicSpirit
Established Member
I would squash as many serveries as I could per hour through the core. I don't really mind where the trains go to terminate after that. I would be tempted to limit the geographical extent of those terminating locations to help with service resilience & depot requirements. I would, however, try to run a simple clock face timetable with trains to those terminating locations at the same minutes every hour and try and spread out the load.
That's pretty much what I was thinking. Most of the answers here don't solve one of the main problems: Thameslink is trying to be all things to all people, by mixing up metro and mainline services and running to far too many destinations, which massively complicates the timetable and leaves it open to disruption spreading through the network.
I'm not sure exactly what I would do, however, the principle I would follow would be to use Thameslink to run very frequent services to a few destinations. I'd also aim to emphasize metro over mainline services - since I think metro tend to be more suitable for running through London in order to enable easy journeys for people travelling within London. That would probably mean, that North of the Thames, I'd focus on maximising frequencies on the St. Albans-Bedford route, and using whatever capacity is left over to supplement the Stevenage/Welwyn/Hertford stoppers on the East Coast line. South of the Thames - less certain, but probably focus services through London Bridge on the metro routes through East/West Croydon. And have the Elephant and Castle services terminate at Blackfriars. Keep the mainline Bedford-Brighton trains only really because those are historically established, but I would try to avoid adding any more 'fast' services.