Limebank Station: Passenger pick-up and drop-off area relocation: December 12 2025 -
At 10:00 am on Thursday, December 18, Town Square Road and the connector road at Limebank Station will re-open to general traffic. As a result, the temporarily-relocated passenger pick-up and drop-off zone will be moved back to its original location, on the north side of Limebank Station.
Customers are reminded to use the designated pedestrian crossing zones when travelling between the O-Train station and the passenger pick-up and drop-off area.
Routes 70, 73, 74, 99, 110, 198, 283, 299 will continue to follow a detour by entering and exiting Limebank Station via Limebank Road.
Detour routing
99 Limebank: From Limebank, right onto Limebank Station Bus Only Roadway, Loop around bus loop, right onto Connector Roadway, continue regular route (and regular service stops within Limebank Station).
99 Barrhaven Centre: From Limebank Station, loop around bus loop, right onto Connector Roadway, left onto Limebank, continue regular route.
110 Limebank: From Earl Armstrong, right onto Limebank, right onto Limebank Station Bus Only Roadway, Loop around bus loop, right onto Connector Roadway, continue regular route (and regular service stops within Limebank Station).
110 Innovation: No detour required.
70, 73, 74, 198, 283, 299 Limebank: From Earl Armstrong, right onto Limebank, right onto Limebank Station Bus Only Roadway, Loop around bus loop, right onto Connector Roadway, continue regular route (and regular service stops within Limebank Station).
70, 73, 74, 198, 283, 299 Outbound trips: From Limebank Station, loop around bus loop, right onto Connector Roadway, left onto Limebank, left onto Earl Armstrong, continue regular route.
Maps (effective December 18)+1 more notice
No 70 trips cancelled now · 5 did not run in novembreCancellations →
Previous measure: 71,6% of arrivals were within five minutes of the timetable (150.278 arrivals over 27 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.
70
Linea 70: Fallowfield ⇄ Limebank & CFIA ~ ACIA
Ogni 15-30 min
Direzione Fallowfield4 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)
Next: 22.5 min after the pairNext: 20.1 min after the pair70707070
Trips in the published timetable marked cancelled without qualifying later matching vehicle observations in our archive. This does not prove the trip did not operate. Not counted: 6 trips with qualifying later matching vehicle observations. Trips with any notice: 12.
Trips needing investigation
9
9 of 623 trips with a usable feed window (1,4%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
614 with position · 9 to investigate · 0 excluded · 623 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 4 nov 2026, 19:01.
Coverage, exclusions and sources
0 of 12 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.
0 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 614 / 623 (98,6%). This is not a delivered-service rate. 7 service days in this source.
Timetables retained before the service day: 7 / 7 requested days · 0 missing days.
Historical calculation: 4 nov 2026, 18:09
Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.
What does the evidence show?
Predictions against the timetable
71,6%
of eligible provider predictions were within five minutes of the timetable.
Within five minutesOutside
Predictions in the source
150.278
Weekdays with evidence
19
Evidence window
6 ott 2026 – 3 nov 2026
The hours we have evidence for
484% · 822 predictions · 14 days
588% · 2161 predictions · 14 days
687% · 4500 predictions · 14 days
787% · 6287 predictions · 14 days
876% · 5640 predictions · 14 days
981% · 3920 predictions · 14 days
1086% · 3527 predictions · 14 days
1175% · 3740 predictions · 14 days
1282% · 3775 predictions · 14 days
1376% · 3733 predictions · 14 days
1470% · 3732 predictions · 14 days
1552% · 4150 predictions · 14 days
1660% · 6002 predictions · 14 days
1758% · 6265 predictions · 14 days
1859% · 5971 predictions · 14 days
1978% · 4533 predictions · 14 days
2073% · 3616 predictions · 14 days
2166% · 3431 predictions · 14 days
2259% · 2106 predictions · 14 days
2384% · 1455 predictions · 14 days
Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.
These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.
Calculated: 4 nov 2026
2 partial-capture days not counted.
What about time of day?
20 hourly cohorts meet the thresholds of 30 predictions and 5 service days. Hourly thresholds are assessed separately from the route-wide aggregate.
Improvement or decline requires comparable periods. This single result cannot establish a trend.
Last 28 days, 7 ottobre 2026 to 3 novembre 2026: 26 days counted.
2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: 8 ottobre 2026, 15 ottobre 2026.
Primo mattino (dalle 4 alle 6)2%
Ora di punta del mattino (dalle 6 alle 9)3%
Metà giornata (dalle 9 del mattino alle 3 del pomeriggio)1%
Ora di punta pomeridiana (dalle 3 alle 6 del pomeriggio)5%
Sera (dalle 6 alle 10 di sera)2%
Notte (dalle 10 di sera alle 4 del mattino)1%
Valori e interpretazione
2% of back-to-back buses on this route arrived bunched together: 2976 of 120.644 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
2% of pairs (2149) had a long gap: more than 1.75 times the planned wait between them.
Autobus che arrivano ravvicinati
Ora del giorno
Coppie verificate
Corse ravvicinate
Lungo intervallo
Primo mattino (dalle 4 alle 6)
2321
2% (41)
0% (1)
Ora di punta del mattino (dalle 6 alle 9)
23.898
3% (598)
2% (591)
Metà giornata (dalle 9 del mattino alle 3 del pomeriggio)
35.748
1% (278)
0% (101)
Ora di punta pomeridiana (dalle 3 alle 6 del pomeriggio)
Lavori stradali e chiusure di strade per eventi pubblicati dalla Città di Ottawa, misurati come vicini al percorso di questa linea. Vicino non prova che l'autobus sia deviato. Per questo, controlli gli avvisi dell'esercente.
Al momento non è possibile leggere l'elenco dei lavori stradali della Città.
A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.
Fonte: eventi di traffico della Città di Ottawa (lavori stradali e chiusure). Contiene informazioni concesse in licenza ai sensi della Open Government Licence, City of Ottawa. La Città precisa che questo elenco è fornito al meglio delle sue possibilità e può essere incompleto. Mappa del traffico della Città di Ottawa ↗
20 scheduled trips with counted cancellation notices from mer 7 ott to mar 3 nov.
Not counted: 24 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Ore con più cancellazioni: 17 (7), 16 (4), 15 (3)
Ultime corse cancellate
dom 1 nov, scheduled 19:52
gio 29 ott, scheduled 15:55
gio 29 ott, scheduled 15:40
mer 28 ott, scheduled 17:10
mer 28 ott, scheduled 16:45
OC Transpo non indica un motivo per le singole corse, quindi non ne viene mostrato nessuno.
Did not come (no bus seen, no notice), last 7 days: 5 of 623 trips we could check.
Aprire l'analisi datata delle previsioni
Verdetto
What this route needs
Median provider predictions are 3,6 to 3,9 min later than the timetable in 6 hours of the day.
Predictions near the start are about 2,9 min later than the timetable, with a similar difference near the end. This does not establish the cause.
15:00 has 52% of predictions within five minutes of the timetable, against 76% the rest of the day.
Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.
Final provider predictions within five minutes of the timetable, by hour, last 14 days, 22 hours with samples
00:00: not enough data00
01:00: not enough data01
02:00: not enough data02
03:00: not enough data03
04:00: 83,7% of final predictions within five minutes of the timetable, 822 predictions, typically 1,5 min late04
05:00: 88,4% of final predictions within five minutes of the timetable, 2161 predictions, typically 0,3 min late05
06:00: 87,2% of final predictions within five minutes of the timetable, 4500 predictions, typically 1,1 min late06
07:00: 87,4% of final predictions within five minutes of the timetable, 6287 predictions, typically 1 min late07
08:00: 75,7% of final predictions within five minutes of the timetable, 5640 predictions, typically 1,8 min late08
09:00: 81,2% of final predictions within five minutes of the timetable, 3920 predictions, typically 1,9 min late09
10:00: 85,7% of final predictions within five minutes of the timetable, 3527 predictions, typically 1,5 min late10
11:00: 75,2% of final predictions within five minutes of the timetable, 3740 predictions, typically 1,7 min late11
12:00: 82,2% of final predictions within five minutes of the timetable, 3775 predictions, typically 1,6 min late12
13:00: 76,3% of final predictions within five minutes of the timetable, 3733 predictions, typically 2,3 min late13
14:00: 70% of final predictions within five minutes of the timetable, 3732 predictions, typically 2,3 min late14
15:00: 51,6% of final predictions within five minutes of the timetable, 4150 predictions, typically 4,8 min late15
16:00: 59,6% of final predictions within five minutes of the timetable, 6002 predictions, typically 4 min late16
17:00: 58% of final predictions within five minutes of the timetable, 6265 predictions, typically 3,7 min late17
18:00: 58,6% of final predictions within five minutes of the timetable, 5971 predictions, typically 3,9 min late18
19:00: 78,2% of final predictions within five minutes of the timetable, 4533 predictions, typically 2,3 min late19
20:00: 72,9% of final predictions within five minutes of the timetable, 3616 predictions, typically 2,7 min late20
21:00: 66,2% of final predictions within five minutes of the timetable, 3431 predictions, typically 3,3 min late21
22:00: 58,8% of final predictions within five minutes of the timetable, 2106 predictions, typically 3,8 min late22
23:00: 83,8% of final predictions within five minutes of the timetable, 1455 predictions, typically 1,9 min late23
90% or more of predictions within five minutes
80 to 90% of predictions within five minutes
under 80% of predictions within five minutes
not enough data
Findings
What
Quando
Misurato
Scenario or next investigation
Problem!Predictions later than timetable
15:00 to 19:00 · 21:00 to 23:00
3,9 min late · 3,6 min late
Recovery time at the terminal
Problem!One hour has a lower prediction match
15:00
52%
Operations, not the timetable
Measurements
Predictions later than timetable · 15:00 to 19:00
Measured arrivals 22.388
Hours affected 4
Spread 13,7 min
Median delay 3,9 min
Suggested running time change 3,9 min
Predictions later than timetable · 21:00 to 23:00
Measured arrivals 5537
Hours affected 2
Spread 10,6 min
Median delay 3,6 min
Suggested running time change 3,6 min
One hour has a lower prediction match · 15:00
Ora 15:00
In orario 51,6%
Measured arrivals 4150
Shortfall 24,4 pts
Route median on time 76%
15:00 57 → to 6115:00 59 → to 6316:00 49 → to 5316:00 59 → to 6317:00 58 → to 6217:00 59 → to 6318:00 55 → to 5918:00 57 → to 6121:00 49 → to 5321:00 51 → to 5522:00 49 → to 5322:00 52 → to 56
Aprire storico, affidabilità e analisi della linea
Verifica della linea
How route 70 has been running
Un breve riepilogo di ciò che sappiamo. Lo diciamo quando non possiamo rispondere a una domanda.
In sintesi
Le previsioni del fornitore sono spesso risultate diverse dall'orario; gli arrivi effettivi non sono stati misurati in modo indipendente.
Dimensione del campione delle previsioni: Campione più ampio
Based on 150.278 eligible provider predictions over 27 measured days, from 6 ott 2026 to 3 nov 2026.
Updated 4 nov 2026, 18:32
Dove e quando le previsioni sono state diverse più volte?
Sono differenze ripetute tra previsione e orario, non disservizi misurati in modo indipendente. Usano le stesse previsioni idonee del risultato qui sopra, ma sono raggruppate per fermata anziché per ora, quindi gli elenchi possono non coincidere riga per riga.
15–16: 48 in 100 eligible predictions differed from the timetable by more than 5 minutes (4150 predictions over 14 days).
17–18: 42 in 100 eligible predictions differed from the timetable by more than 5 minutes (6265 predictions over 14 days).
18–19: 41 in 100 eligible predictions differed from the timetable by more than 5 minutes (5971 predictions over 14 days).
22–23: 41 in 100 eligible predictions differed from the timetable by more than 5 minutes (2106 predictions over 14 days).
2 current notices affect this route
• Limebank Station: Passenger pick-up and drop-off area relocation
• Detour: Routes entering and exiting Limebank Station
42 in 100 eligible predictions differed from the timetable by more than 5 minutes (1269 predictions over 30 days).
Aprire questa fermata
Sono previsioni del fornitore specifiche per la linea, confrontate con l'orario. Mostrano differenze di previsione ripetute in un luogo e a un'ora precisi. Non sono arrivi misurati e non ne indicano la causa.
Controlli ogni corsa e ogni data
Apra un periodo per vedere ogni giorno di servizio, ogni corsa programmata, ogni lacuna nei dati, l'ID del veicolo pubblico osservato e i conteggi esatti alla base di questo riepilogo.
Cosa vogliono sapere i passeggeri
Qualche corsa è cancellata in questo momento?
0 of 12Vengono controllate le corse che partono dai capolinea della linea nelle prossime 4 ore. Non è un tasso storico di cancellazioni.
Possibili corse saltate dopo il controllo delle lacune del feed?
9 of 623 checked trips need a closer look9 of 623 trips with enough public-feed evidence had no matching position over 7 days. 0 of 623 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Come sono differite le previsioni dell'operatore rispetto all'orario?
Quale attesa implicavano le previsioni del fornitore?
7,2 min average predicted wait0,7 min beyond the scheduled wait, based on 279 eligible predictions at 13 high-frequency stops over 12 days.
Verifica della modifica dell'orario
Orario pubblicato: prima e dopo
Questo confronto riguarda l'orario ufficiale conservato attualmente e la versione conservata in precedenza. Le modifiche dell'orario sono fatti su ciò che era stato pianificato. Non provano che una corsa sia stata effettuata.
Current published schedule began 30 ottobre 2026
Giorno di servizio selezionato da ciascun orario pubblicato
Controlliamo il primo lunedì dopo l'inizio del nuovo orario e il lunedì di una settimana prima. Ogni dato proviene dalle versioni GTFS ufficiali conservate indicate qui sotto.
Almeno una data selezionata ha un servizio aggiunto o rimosso nel calendario. Lo consideri un contesto di giorno festivo o di servizio speciale, non una normale crescita dei giorni feriali.
Impronta del feed: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945
Il servizio è migliorato dopo la modifica?
Confronteremo gli arrivi consolidati nei 14 giorni prima e dopo la modifica. Pubblichiamo il confronto solo quando entrambi i periodi hanno almeno 7 giorni di servizio e 200 arrivi.
Still collecting: before has 79.000 arrivals over 14 days; after has 27.511 arrivals over 5 days. No improvement or decline is claimed yet.
I checksum permettono a chiunque di verificare quale orario conservato ha prodotto i conteggi. Una variazione del conteggio non indica una causa, una cancellazione, una decisione dell'esercente o un effetto sui passeggeri.
Come viene valutata questa ligne: Linea regolare con tutte le fermate
Confrontiamo l'ultima previsione idonea del fornitore per ogni arrivo programmato con l'orario ufficiale. Non sono arrivi misurati in modo indipendente. Per un risultato servono almeno 200 previsioni idonee. Qui si usa come obiettivo per i passeggeri "entro 5 minuti".
Che cosa questi dati non possono dimostrare
Il feed pubblico non fornisce conteggi affidabili dei passeggeri né eventi di passeggeri non imbarcati. Una posizione mancante non prova da sola una cancellazione, una mancata corsa, un'inversione anticipata o una causa.
Vedere le definizioni, le soglie e l'ordine dei dati
Feed ufficiale attuale: cancellazioni esplicite, fermate saltate e avvisi attivi.
Osservazioni abbinate: posizioni dei veicoli e previsioni consolidate collegate all'orario ufficiale.
Orario ufficiale: ciò che era previsto, tenuto separato da ciò che è stato osservato.
Segnalazioni di passeggeri e operatori: indizi su linee, orari e luoghi da verificare, non prove numeriche di per sé.
Risultati provvisori, dati probanti pubblicati
Come si sono confrontate le previsioni con l'orario?
Ogni ora confronta l'ultima previsione idonea del fornitore per un arrivo previsto a orario con l'orario ufficiale. «Entro 5 minuti» indica la differenza tra le previsioni, non un arrivo misurato né la prova che un autobus abbia circolato.
Periodo dei dati probatori: 6 ottobre 2026 to 3 novembre 2026
6 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
Autobus previsto a orario, ma non osservato in tempo reale
614 / 623 scheduled trips published at least one position across 1 service days (98,6%).
04:002 / 18 trips without a position88,9%
15:002 / 38 trips without a position94,7%
17:002 / 48 trips without a position95,8%
13:001 / 28 trips without a position96,4%
19:001 / 28 trips without a position96,4%
18:001 / 38 trips without a position97,4%
Questa non è una mancata corsa confermata. Una posizione mancante può indicare una corsa soppressa o saltata, ma può anche indicare un ID di corsa non assegnato o un'interruzione nel feed del gestore. Otranspo pubblica questa mancanza perché è importante per chi viaggia, senza trarre conclusioni non verificate.
Prediction check: the last eligible provider prediction no earlier than ten minutes before the scheduled arrival, counted once per trip, stop and scheduled Toronto calendar date. It is compared with the timetable, not an independently measured arrival. Trip-position check: the timetable kept before each service day, matched to recorded positions. Exact IDs are preferred; an OC timetable suffix is matched only to one trip on the same route and date with an overlapping time window. Missing timetables, ambiguous matches and feed gaps stay labelled; they are not confirmed no-shows. Fonti e limiti.
Dated service
Trips scheduled that day
The timetable, notices and what the live feed says are shown apart. Seeing a bus on the map does not prove you can board it.
November 3, 2026 · 98 trips in the retained timetable · retained notices; capture coverage unverified
In short: 98 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.
04:39– 05:24
Trip 10014030Vehicle position matchedFirst / last feed position: 4:20 a.m. EST / 5:25 a.m. EST; not actual start or end times.
04:41– 04:51
Trip 23449030Vehicle position matchedFirst / last feed position: 4:41 a.m. EST / 4:59 a.m. EST; not actual start or end times.
05:00– 05:52
Trip 33880030Vehicle position matchedFirst / last feed position: 4:22 a.m. EST / 5:57 a.m. EST; not actual start or end times.
05:11– 05:21
Trip 19652030Vehicle position matchedFirst / last feed position: 4:52 a.m. EST / 5:24 a.m. EST; not actual start or end times.
05:27– 06:17
Trip 27697030Vehicle position matchedFirst / last feed position: 5:20 a.m. EST / 6:22 a.m. EST; not actual start or end times.
06:00– 06:52
Trip 7203030Vehicle position matchedFirst / last feed position: 5:40 a.m. EST / 6:54 a.m. EST; not actual start or end times.
06:03– 06:53
Trip 16192030Vehicle position matchedFirst / last feed position: 5:58 a.m. EST / 6:55 a.m. EST; not actual start or end times.
06:15– 07:09
Trip 11066030Vehicle position matchedFirst / last feed position: 6:10 a.m. EST / 7:44 a.m. EST; not actual start or end times.
06:15– 07:07
Trip 27315030Vehicle position matchedFirst / last feed position: 5:56 a.m. EST / 7:08 a.m. EST; not actual start or end times.
06:28– 07:20
Trip 1349030Vehicle position matchedFirst / last feed position: 6:23 a.m. EST / 7:21 a.m. EST; not actual start or end times.
06:29– 07:24
Trip 11574030Vehicle position matchedFirst / last feed position: 6:14 a.m. EST / 7:34 a.m. EST; not actual start or end times.
06:43– 07:41
Trip 36738030Vehicle position matchedFirst / last feed position: 6:24 a.m. EST / 7:49 a.m. EST; not actual start or end times.