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 198 trips cancelled now · 0 did not run in novembreCancellations →

Previous measure: 65% of arrivals were within five minutes of the timetable (6081 arrivals over 18 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.

198

Linea 198: Limebank ⇄ Greenboro

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 29 ott 2026 – 4 nov 2026

Scheduled trips with cancellation notices

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: 1 trips with qualifying later matching vehicle observations. Trips with any notice: 1.

Trips needing investigation

0 of 55 trips with a usable feed window (0%) had no matching position.

These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.

55 with position · 0 to investigate · 0 excluded · 55 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 5 nov 2026, 01:36.

Coverage, exclusions and sources

0 scheduled trips were excluded from the position check for feed or identity gaps.

Published position coverage: 55 / 55 (100%). 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: 5 nov 2026, 00: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

65%

of eligible provider predictions were within five minutes of the timetable.

Predictions in the source: 6081
Weekdays with evidence: 18
Evidence window: 6 ott 2026 – 3 nov 2026

The hours we have evidence for

5100% · 33 predictions · 11 days
684% · 704 predictions · 11 days
791% · 627 predictions · 11 days
895% · 407 predictions · 11 days
1521% · 248 predictions · 11 days
1650% · 532 predictions · 11 days
1736% · 660 predictions · 11 days
1853% · 420 predictions · 9 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: 5 nov 2026

2 partial-capture days not counted.

What about time of day?

8 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.

Explore the dated evidence Source of this result

Autobus che arrivano ravvicinati

Last 28 days, 8 ottobre 2026 to 4 novembre 2026: 25 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.

Valori e interpretazione

4% of back-to-back buses on this route arrived bunched together: 17 of 482 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (0) 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
Ora di punta pomeridiana (dalle 3 alle 6 del pomeriggio)	482	4% (17)	0% (0)

Come viene misurato →How we got this numberBus ravvicinati e punti lenti su ogni linea →

Dove questa linea è più lenta

Slowest: LIMEBANK A to RIVERVIEW B, 19,3 km/h actual against 30,8 km/h planned.

Dove questa linea è più lenta
Da	A	Distanza	Velocità prevista	Velocità effettiva	Corse misurate	Corse lente
LIMEBANK A	RIVERVIEW B	2,6 km	30,8 km/h	19,3 km/h	92	53%
SOUTH KEYS E	RIVERSIDE / HUNT CLUB	3,9 km	21,8 km/h	20,5 km/h	76	11%
GREENBORO B	SOUTH KEYS E	830 m	20,9 km/h	24,1 km/h	65	11%
RIVERVIEW B	RIVER / LEITRIM	2,7 km	27,3 km/h	26,3 km/h	92	5%
RIVER / LEITRIM	RIVERVIEW A	2,7 km	30,4 km/h	28,3 km/h	76	14%
HUNT CLUB / RIVERSIDE	SOUTH KEYS A	4,1 km	31 km/h	29,9 km/h	89	3%
RIVER / LEITRIM	HUNT CLUB / RIVERSIDE	4,8 km	28,5 km/h	40,7 km/h	91	3%
RIVERSIDE / HUNT CLUB	RIVER / LEITRIM	4,8 km	53,3 km/h	51,4 km/h	76	7%

Un viaggio lento ha richiesto almeno 1.5 volte il tempo previsto.

Come viene misurato →

Lavori stradali della città vicino a questa ligne

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 ↗

Cancellazioni su questa linea

Che cosa significano queste parole →

2 partial-capture days not counted.

1 scheduled trips with counted cancellation notices from gio 8 ott to mer 4 nov.

Not counted: 7 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.

Ore con più cancellazioni: 15 (1)

Ultime corse cancellate

mer 21 ott, scheduled 15:37

OC Transpo non indica un motivo per le singole corse, quindi non ne viene mostrato nessuno.

Non è passata (nessun autobus visto, nessun avviso), ultimi 7 giorni: nessuna delle corse che abbiamo potuto verificare.

Aprire l'analisi datata delle previsioni

Verdetto

What this route needs

Median provider predictions are 6,2 min later than the timetable in 4 hours of the day.

Predictions near the start are about 4,9 min later than the timetable, with a similar difference near the end. This does not establish the cause.

Wide prediction spread 18:00: the 95th percentile is 20,2 min later than the median.

15:00 has 21% of predictions within five minutes of the timetable, against 68% the rest of the day.

Matched public positions cover 100% of scheduled trips. This is a lower bound on operated service, not an audited delivery result.

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, 8 hours with samples

00:00: not enough data
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 100% of final predictions within five minutes of the timetable, 33 predictions, typically 1,3 min late
06:00: 83,5% of final predictions within five minutes of the timetable, 704 predictions, typically 2,3 min late
07:00: 91,1% of final predictions within five minutes of the timetable, 627 predictions, typically 1,7 min late
08:00: 95,1% of final predictions within five minutes of the timetable, 407 predictions, typically 0,3 min late
09:00: not enough data
10:00: not enough data
11:00: not enough data
12:00: not enough data
13:00: not enough data
14:00: not enough data
15:00: 21% of final predictions within five minutes of the timetable, 248 predictions, typically 11,3 min late
16:00: 50,2% of final predictions within five minutes of the timetable, 532 predictions, typically 5 min late
17:00: 35,5% of final predictions within five minutes of the timetable, 660 predictions, typically 7,5 min late
18:00: 52,6% of final predictions within five minutes of the timetable, 420 predictions, typically 4,6 min late. Provider predictions have a wide spread.
19:00: not enough data
20:00: not enough data
21:00: not enough data
22:00: not enough data
23:00: not enough data

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
prediction spread of 20 min or more between the 95th percentile and median

Findings
What	Quando	Misurato	Scenario or next investigation
ProblemPredictions later than timetable	15:00 to 19:00	6,2 min late	Recovery time at the terminal
ProblemWide prediction spread	18:00	20,2 min swing	Operations, not the timetable
ProblemOne hour has a lower prediction match	15:00	21%	Operations, not the timetable
StrengthObserved-position lower bound	All measured hours	100%	Keep what works

Measurements

Predictions later than timetable · 15:00 to 19:00: Measured arrivals 1860; Hours affected 4; Spread 13,1 min; Median delay 6,2 min; Suggested running time change 6,2 min
Wide prediction spread · 18:00: Measured arrivals 420; Hours affected 1; Spread 20,2 min; Median delay 4,6 min; Suggested running time change 4,6 min
One hour has a lower prediction match · 15:00: Ora 15:00; In orario 21%; Measured arrivals 248; Shortfall 47,1 pts; Route median on time 68,1%
Observed-position lower bound · All measured hours: Obiettivo 99,5%; Trips with a matching position 100%; Giorni di servizio 5; Trips with a matching position 55; Corse programmate 55

Aprire storico, affidabilità e analisi della linea

Verifica della linea

How route 198 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.

65 in 100 eligible predictions were within 5 minutes of the timetable · 6081 predictions checked

Dimensione del campione delle previsioni: Campione più ampio

Based on 6081 eligible provider predictions over 18 measured days, from 6 ott 2026 to 3 nov 2026.

Updated 5 nov 2026, 00:33

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: 79 in 100 eligible predictions differed from the timetable by more than 5 minutes (248 predictions over 11 days).
17–18: 65 in 100 eligible predictions differed from the timetable by more than 5 minutes (660 predictions over 11 days).
16–17: 50 in 100 eligible predictions differed from the timetable by more than 5 minutes (532 predictions over 11 days).
18–19: 47 in 100 eligible predictions differed from the timetable by more than 5 minutes (420 predictions over 9 days).

2 current notices affect this route

• Limebank Station: Passenger pick-up and drop-off area relocation
• Detour: Routes entering and exiting Limebank Station

Differenze di previsione per fermata

RIVER / SHORELINE PATHWAY
71 in 100 eligible predictions differed from the timetable by more than 5 minutes (117 predictions over 20 days).
Aprire questa fermata
RIVER / AD. 540
68 in 100 eligible predictions differed from the timetable by more than 5 minutes (117 predictions over 20 days).
Aprire questa fermata
RIVER / HONEY GABLES
65 in 100 eligible predictions differed from the timetable by more than 5 minutes (117 predictions over 20 days).
Aprire questa fermata
RIVER / RYEBURN
64 in 100 eligible predictions differed from the timetable by more than 5 minutes (117 predictions over 20 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?: Nessuna corsa parte nelle prossime 4 oreVengono 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?: 0 of 55 checked trips need a closer look0 of 55 trips with enough public-feed evidence had no matching position over 7 days. 0 of 55 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?: At the 95th percentile, the predicted difference was 18,1 min (positive means later; negative means earlier)65 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
Quale attesa implicavano le previsioni del fornitore?: Nessun risultato per singola ligne raggiunge ancora la soglia dei dati probanti. Ciò non significa che le interruzioni non siano avvenute.

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.

Prima

Data di servizio verificata: 26 ottobre 2026

Corse programmate: 11
Fermate previste all'orario distinte: 66
Percorsi pubblicati distinti: 2
Fascia oraria del servizio pubblicata: 5:57–18:56

Operator calendar-date records: 0 added · 2 removed

Impronta del feed: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

Nuovo orario

Data di servizio verificata: 2 novembre 2026

Corse programmate: 11
Fermate previste all'orario distinte: 66
Percorsi pubblicati distinti: 2
Fascia oraria del servizio pubblicata: 5:57–18:56

Operator calendar-date records: 0 added · 2 removed

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 3284 arrivals over 10 days; after has 1331 arrivals over 4 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

Entro 5 minuti dall'orario: 65,0%
Previsioni idonee verificate: 6081
Giorni feriali con dati: 18
Ritardo previsto al 95º percentile: 18,1 min late

Patterns by hour (8)

Patterns by hour (8)
Ora	In orario	Mediana	95º percentile	Dati probanti
05:00	100,0%	1,3 min late	3,8 min late	33 · 11 days
06:00	83,5%	2,3 min late	7,1 min late	704 · 11 days
07:00	91,1%	1,7 min late	5,9 min late	627 · 11 days
08:00	95,1%	0,3 min late	4,6 min late	407 · 11 days
15:00	21,0%	11,3 min late	16,9 min late	248 · 11 days
16:00	50,2%	5 min late	13,6 min late	532 · 11 days
17:00	35,5%	7,5 min late	25,1 min late	660 · 11 days
18:00	52,6%	4,6 min late	24,8 min late	420 · 9 days

4 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

55 / 55 scheduled trips published at least one position across 5 service days (100,0%).

05:000 / 5 trips without a position100,0%
06:000 / 10 trips without a position100,0%
07:000 / 10 trips without a position100,0%
15:000 / 5 trips without a position100,0%
16:000 / 10 trips without a position100,0%
17:000 / 10 trips without a position100,0%

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.

Service day

November 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

November 4, 2026 · 11 trips in the retained timetable · retained notices; capture coverage unverified

In short: 11 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.

05:57– 06:20
Trip 12749040Vehicle position matchedFirst / last feed position: 5:27 a.m. EST / 6:48 a.m. EST; not actual start or end times.
06:44– 07:13
Trip 7831040Vehicle position matchedFirst / last feed position: 6:30 a.m. EST / 7:42 a.m. EST; not actual start or end times.
06:48– 07:13
Trip 12264040Vehicle position matchedFirst / last feed position: 6:49 a.m. EST / 7:29 a.m. EST; not actual start or end times.
07:43– 08:16
Trip 28012040Vehicle position matchedFirst / last feed position: 7:34 a.m. EST / 8:25 a.m. EST; not actual start or end times.
07:48– 08:20
Trip 15143040Vehicle position matchedFirst / last feed position: 7:43 a.m. EST / 8:20 a.m. EST; not actual start or end times.
15:37– 16:09
Trip 34447040Vehicle position matchedFirst / last feed position: 3:25 p.m. EST / 4:24 p.m. EST; not actual start or end times.
16:06– 16:38
Trip 11881040Vehicle position matchedFirst / last feed position: 3:43 p.m. EST / 4:41 p.m. EST; not actual start or end times.
16:44– 17:17
Trip 6054040Vehicle position matchedFirst / last feed position: 4:19 p.m. EST / 5:28 p.m. EST; not actual start or end times.
17:08– 17:40
Trip 36020040Vehicle position matchedFirst / last feed position: 4:48 p.m. EST / 5:40 p.m. EST; not actual start or end times.
17:45– 18:17
Trip 10364040Vehicle position matchedFirst / last feed position: 5:18 p.m. EST / 6:18 p.m. EST; not actual start or end times.
18:24– 18:56
Trip 35953040Vehicle position matchedFirst / last feed position: 6:19 p.m. EST / 6:52 p.m. EST; not actual start or end times.