(25 Jul 2022, 7:06 pm)S813 FVK wrote Not sure why, but it's not too uncommon for buses to apparently track as one service when they're actually NIS
Another backdated example, also the 78: https://bustimes.org/vehicles/40087?date=2022-07-20#
And another for a deadrun between Stanley and CLS showing 21: https://bustimes.org/vehicles/39821?date=2022-07-18
Bustimes takes its data from Ticketer. Drivers selecting trips in error on Ticketer will therefore show up on Bustimes.
Instances can include a driver accepting their next trip after their break while logging off their last run before their break, or selecting an incorrect duty and not realising until after they've then also accepted the first trip of said incorrect duty.