Can you imagine the 'Next Stop' screen? It must be working overtime!The X18 from Newcastle to Berwick via the coast comes in at a whopping 158 stops according to Google
The N9 looks to come in at ~80.Not a UK record, but the X26 in London comes in at 70 stops - is that a London record?
The X18 from Newcastle to Berwick via the coast comes in at a whopping 158 stops according to Google
N89 has approximately 107The N9 looks to come in at ~80.
I think I can beat that - route 35 between Aberdeen and Elgin seems to have a staggering 160 stops!
That figure is wildly wrong - it is a limited stop route and only has 14 stops.Not a UK record, but the X26 in London comes in at 70 stops - is that a London record?
That figure is wildly wrong - it is a limited stop route and only has 14 stops.
In Wales, the 132 Cardiff-Maerdy has 95. Can anyone find a 100+?
Trip.objects.annotate(count=Count('stoptime')).order_by('-count')
I never knew the villager (it lost the V1 around 2 years ago) was registered as a circular route. I suppose it is because of the circular route around Burton but then again the X38 is registered with a 'outbound' and 'inbound' and that run the opposite way round the circle the villager does in Burton.I've queried the bustimes.org database:
- 35 - Elgin - Aberdeen – a couple of journeys have 165 stops
- Trent Barton V1 – 163 stops. Sort of cheating as it's registered as a circular – a very squashed circle.
- Yorkshire Coastliner 843 – 160 stops
- T2 - Bangor - Aberystwyth – 158 stops
- Squarepeg 9 - Wortley - White Rose Centre – a couple of journeys have 158 stops
Code:Trip.objects.annotate(count=Count('stoptime')).order_by('-count')
I never knew the villager (it lost the V1 around 2 years ago) was registered as a circular route. I suppose it is because of the circular route around Burton but then again the X38 is registered with a 'outbound' and 'inbound' and that run the opposite way round the circle the villager does in Burton.
I think that is because they are still using the same bus registration looking at the gov website which was back when the V3 (now run by spare buses) was part of the villager brand as well as the service number in both has 'villager V1' and 'villager V3'. Other than the council run live bus screens there is no mention of the number V1 on the ground.It appears to still have the V1 name on the published timetable data.
It's still listed as the V1 in trentbarton's data feed which is linked from the link I posted. That's probably why the council's screens say it too.I think that is because they are still using the same bus registration looking at the gov website which was back when the V3 (now run by spare buses) was part of the villager brand as well as the service number in both has 'villager V1' and 'villager V3'. Other than the council run live bus screens there is no mention of the number V1 on the ground.