STO · Rapibus service

Route 200

Lorrain, Ottawa

Explore the route

Choose a destination, then select a stop on the map or route diagram.

3 official stop patterns

0 verified representative shapes · 32 stops

Dashed lines connect the published stop order; they are not claimed street paths

Map source and limits

A solid line matches one published representative trip whose stops and order were checked. Another trip with the same stops may follow a different shape. Dashed lines connect published stops only; they do not describe streets.

This view does not show live vehicle positions.

Open the full-screen map

All published paths

Where does it go?

Different journeys can take different branches. Choose a published path above to see its stops in order.

You can also select any stop on the map to open its departure board.

Lorrain1 official stop pattern

Ottawa2 official stop patterns

Published stop order does not prove that a vehicle is running now.

Schedule and source records

CENTRE RIDEAU to STATION LORRAIN arrêt d'arrivée · 16 stops

Scheduled from Sep 28, 2026 to Nov 20, 2026

This service is published only as specific added dates, not as a weekly calendar.

3 official service records

39 added dates and 0 removed dates

Open this scheduled trip progression

Review the official service records

Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026

Service records for this stop pattern

Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026

STATION LORRAIN to CENTRE RIDEAU · 16 stops

Scheduled from Sep 28, 2026 to Nov 20, 2026

This service is published only as specific added dates, not as a weekly calendar.

3 official service records

39 added dates and 0 removed dates

Open this scheduled trip progression

Review the official service records

Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026

Service records for this stop pattern

Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026

Station LABROSSE #1 to CENTRE RIDEAU · 14 stops

Scheduled from Sep 28, 2026 to Nov 20, 2026

This service is published only as specific added dates, not as a weekly calendar.

3 official service records

39 added dates and 0 removed dates

Open this scheduled trip progression

Review the official service records

Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026

Service records for this stop pattern

Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:200
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026

Official feed version ca455c71-c30a-4e4d-8b72-2709212731cd

Source checksum a7e1f22955084828484cca5e8f1ebff9e785c70984ad5dd93b872a5d64ace6e4

Schedule and accessibility details

Current service date: Oct 8, 2026
Selected direction: Every published direction
Imported schedule valid through: Nov 22, 2026

All imported trips are marked accessible.

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 1, 2026 – Oct 7, 2026

Scheduled trips with cancellation notices

—

No retained notice returned; this does not prove zero cancellations. 1 partial-capture day not counted.

Trips needing investigation

8 of 240 trips with a usable feed window (3.3%) had no matching position.

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

232 with position · 8 to investigate · 60 excluded · 300 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Oct 8, 2026, 2:39 a.m..

Coverage, exclusions and sources

0 of 7 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.

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

Published position coverage: 232 / 300 (77.3%). 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: Oct 8, 2026, 1:18 a.m.

Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.

Cancellations on this route

What these words mean →

1 partial-capture day not counted.

No counted cancellations on this route in the last four weeks. Notices we could not check would be listed below.

Did not come (no bus seen, no notice), last 7 days: 8 of 240 trips we could check.

Buses arriving bunched

Bunching and slow spots on every route →

Not measured yet. The daily count has not reached these days, so there is no number to show.

City road work near this route

Road work and event road closures the City of Ottawa has published, measured as near this route’s path. Near is not proof that the bus is detoured: check the operator’s own alerts for that.

Road work
Elgin S/B between Queen and Albert
Jul 20, 2026, 12:00 a.m. to Oct 30, 2026, 5:00 p.m.
Elgin southbound right lane closed between Queen and Albert due to construction, until October 30th.
The City marks this as affecting transit.
about 1 m from the route
City record updated Sep 4, 2026, 8:24 a.m..
Road work
ALBERT at LYON
Dates not published
Albert and Lyon off-peak lane reductions at the intersection due to construction.
about 3 m from the route
City record updated Sep 9, 2026, 6:32 p.m..

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.

Source: City of Ottawa traffic events (road work and closures). Contains information licensed under the Open Government Licence, City of Ottawa. The City says this list is best effort and may be incomplete. City of Ottawa traffic map ↗

When this route is usually busy

From the load level STO’s buses report, over the last eight weeks. A time is marked usually busy when at least half of the trips with a reading reached standing room or fuller.

No time of day was usually busy in the last eight weeks.

When this route is usually busy	Weekdays	Saturdays	Sundays
Before 6 am	Not enough readings	Not enough readings	Not enough readings
6 to 9 am	Usually seats46.7% of 887 trips	Not enough readings	Not enough readings
9 am to 3 pm	Usually seats4% of 75 trips	Not enough readings	Not enough readings
3 to 6 pm	Usually seats43.5% of 860 trips	Not enough readings	Not enough readings
6 to 10 pm	Usually seats16.9% of 77 trips	Not enough readings	Not enough readings
After 10 pm	Not enough readings	Not enough readings	Not enough readings

Based on 55 computed days.

Source: the occupancy status in STO’s public real-time vehicle feed, which STO sets from each bus’s load sensor (seats available under 60% full, standing room under 90%, full above 90%).
Each trip counts once per time of day, at the highest load it reported.
Reports of an empty bus are left out, because older records could not tell an empty bus from one with no sensor.
A time of day needs at least 12 trips on at least 4 different days before anything is shown. Holidays are counted with their day of the week.

What does the evidence show?

Predictions against the timetable

78.4%

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

These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.

Predictions in the source: 17,572
Weekdays with evidence: 20
Evidence window: Sep 8, 2026 – Oct 6, 2026

Calculated: Oct 8, 2026

1 partial-capture day not counted.

Explore the dated evidence Source of this result

The hours we have evidence for

Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.

92%6 a.m.946 predictions · 10 days
88%7 a.m.1,958 predictions · 10 days
82%8 a.m.1,344 predictions · 10 days
84%9 a.m.63 predictions · 9 days
86%3 p.m.930 predictions · 9 days
70%4 p.m.1,592 predictions · 9 days
74%5 p.m.1,371 predictions · 9 days
77%6 p.m.95 predictions · 9 days

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.

Open the dated prediction analysis

Verdict

What this route needs

Predicted waits All measured hours are 1.2 min longer than scheduled waits.

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: not enough data
06:00: 91.8% of final predictions within five minutes of the timetable, 946 predictions, typically 0.5 min late
07:00: 88.4% of final predictions within five minutes of the timetable, 1,958 predictions, typically 0.6 min late
08:00: 81.5% of final predictions within five minutes of the timetable, 1,344 predictions, typically 1.3 min late
09:00: 84.1% of final predictions within five minutes of the timetable, 63 predictions, typically 1.2 min late
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: 86.1% of final predictions within five minutes of the timetable, 930 predictions, typically 1.2 min late
16:00: 70% of final predictions within five minutes of the timetable, 1,592 predictions, typically 1.9 min late
17:00: 73.7% of final predictions within five minutes of the timetable, 1,371 predictions, typically 1.3 min late
18:00: 76.8% of final predictions within five minutes of the timetable, 95 predictions, typically 1.1 min late
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

Findings
What	When	Measured	Scenario or next investigation
ProblemPredicted spacing varies	All measured hours	1.2 min extra wait	Manage the headway

Measurements

Predicted spacing varies · All measured hours: Stops 32; Extra wait share 41.2%; Matched arrivals 14,674; Extra wait 1.2 min; Scheduled wait 3 min

Open history, reliability and route analysis

Route check

How route 200 has been running

A short summary of what we know. We say so when we cannot answer a question.

Bottom line

Provider predictions often differed from the timetable; actual arrivals were not independently measured.

78 in 100 eligible predictions were within 5 minutes of the timetable · 17,572 predictions checked

Prediction sample size: Larger sample

Based on 17,572 eligible provider predictions over 20 measured days, from Sep 8, 2026 to Oct 6, 2026.

Updated Oct 8, 2026, 1:33 a.m.

Where and when did predictions differ repeatedly?

These are repeated prediction-to-timetable differences, not independently measured service failures. They use the same eligible predictions as the result above, but group by stop rather than hour, so the lists need not match line for line.

No repeated prediction-difference period has cleared the evidence threshold yet.

No current official notice matches this route.

Prediction differences by stop

Station GOUIN
36 in 100 eligible predictions differed from the timetable by more than 5 minutes (566 predictions over 20 days).
Open this stop
WELLINGTON/LYON
36 in 100 eligible predictions differed from the timetable by more than 5 minutes (547 predictions over 20 days).
Open this stop
Station MONTCALM bretelle dir nord #2
36 in 100 eligible predictions differed from the timetable by more than 5 minutes (564 predictions over 20 days).
Open this stop
STATION LORRAIN arrêt d'arrivée
35 in 100 eligible predictions differed from the timetable by more than 5 minutes (564 predictions over 20 days).
Open this stop

These are route-specific provider predictions compared with the timetable. They identify repeated prediction differences at a place and time, not measured arrivals or their cause.

Check every trip and date

Open a time period to see each service day, scheduled trip, feed gap, observed public vehicle ID, and the exact counts behind this summary.

What riders want to know

Is any trip cancelled right now?: 0 of 7Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 8 of 240 checked trips need a closer look8 of 240 trips with enough public-feed evidence had no matching position over 7 days. 60 of 300 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
How did provider predictions differ from the timetable?: At the 95th percentile, the predicted difference was 11.1 min (positive means later; negative means earlier)78 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: 4.2 min average predicted wait1.2 min beyond the scheduled wait, based on 14,674 eligible predictions at 32 high-frequency stops over 18 days.

Schedule change check

Published schedule: before and after

This compares the current retained official schedule with the prior retained version. Schedule changes are facts about what was planned; they do not prove that a trip ran.

Current published schedule began September 27, 2026

Selected service day from each published schedule

We check the first Monday after the new schedule began and the Monday one week earlier. Every figure comes from the retained official GTFS versions named below.

At least one selected date uses added or removed calendar-date service. Treat this as holiday or special-service context, not ordinary weekday growth.

Before

Service date checked: September 21, 2026

Scheduled trips: 0
Distinct scheduled stops: 0
Distinct published paths: 0
Published service span: —–—

Feed fingerprint: a1fd9699f40664cc · 1a4ea4f3-91a8-43db-8c05-e3b01b5bf24c

New schedule

Service date checked: September 28, 2026

Scheduled trips: 60
Distinct scheduled stops: 32
Distinct published paths: 3
Published service span: 6:07 a.m.–6:12 p.m.

Operator calendar-date records: 1 added · 0 removed

Feed fingerprint: a7e1f22955084828 · ca455c71-c30a-4e4d-8b72-2709212731cd

Did service improve after the change?

We will compare settled arrivals for the 14 days before and after the change. We publish the comparison only after both sides have at least 7 service days and 200 arrivals.

Before

September 13, 2026 – September 26, 2026

77.8 in 100 arrivals were within 5 minutes

Average: 2.2 min from schedule

Slowest 5 in 100: about 10.8 min late

8,775 · 10 days

New schedule

September 27, 2026 – October 7, 2026

82.1 in 100 arrivals were within 5 minutes

Average: 1.7 min from schedule

Slowest 5 in 100: about 10.3 min late

6,107 · 7 days

Checksums let anyone verify which retained timetable produced the counts. A changed count does not identify a cause, cancellation, operator decision, or passenger impact.

How this route is judged: Rapibus rapid transit

We compare the last eligible provider prediction for each scheduled arrival with the official schedule. These are not independently measured arrivals. A result needs at least 200 eligible predictions. Within 5 minutes is the rider-facing target used here.

What this data cannot prove

The public feed does not provide dependable passenger counts or passed-up-rider events. A missing position does not by itself prove a cancellation, no-show, short turn or cause.

See the definitions, thresholds and evidence order

Official current feed: explicit cancellations, skipped stops and active notices.
Matched observations: vehicle positions and settled predictions tied to the official schedule.
Official timetable: what was planned, kept separate from what was observed.
Rider and operator reports: leads about routes, times and places to investigate, not numeric proof by themselves.

Provisional results, published evidence

How did predictions compare with the timetable?

Each hour compares the last eligible provider prediction for a scheduled arrival with the timetable. “Within 5 minutes” describes that prediction difference, not a measured arrival or proof that a bus ran.

Evidence window: September 8, 2026 to October 6, 2026

Within 5 minutes of schedule: 78.4%
Eligible predictions checked: 17,572
Weekdays with data: 20
95th-percentile predicted delay: 11.1 min late

Patterns by hour (8)

Patterns by hour (8)
Hour	On time	Median	95th percentile	Evidence
06:00	91.8%	0.5 min late	5 min late	946 · 10 days
07:00	88.4%	0.6 min late	6 min late	1,958 · 10 days
08:00	81.5%	1.3 min late	9.4 min late	1,344 · 10 days
09:00	84.1%	1.2 min late	6.6 min late	63 · 9 days
15:00	86.1%	1.2 min late	9 min late	930 · 9 days
16:00	70.0%	1.9 min late	14.3 min late	1,592 · 9 days
17:00	73.7%	1.3 min late	10.9 min late	1,371 · 9 days
18:00	76.8%	1.1 min late	10.8 min late	95 · 9 days

No repeated pattern below 70% is yet established across at least three service days.

Scheduled bus, but not observed in realtime

232 / 240 scheduled trips published at least one position across 4 service days (96.7%).

16:003 / 48 trips without a position93.8%
06:002 / 40 trips without a position95.0%
15:002 / 44 trips without a position95.5%
17:001 / 24 trips without a position95.8%
07:000 / 60 trips without a position100.0%
08:000 / 20 trips without a position100.0%

This is not a confirmed no-show. A missing position can mean a cancelled or missed bus, but it can also mean an unassigned trip ID or an operator-feed gap. Otranspo publishes the gap because it matters to riders while keeping the conclusion honest.

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. Sources and limitations.

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

October 7, 2026 October 6, 2026 October 5, 2026 October 4, 2026 October 3, 2026 October 2, 2026 October 1, 2026

October 7, 2026 · 60 trips in the retained timetable · retained notices; capture coverage unverified

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

06:07– 06:45
Trip sto:62731673Vehicle position matchedFirst / last feed position: 6:06 a.m. EDT / 6:41 a.m. EDT; not actual start or end times.
06:08– 06:51
Trip sto:62731674Vehicle position matchedFirst / last feed position: 6:01 a.m. EDT / 6:44 a.m. EDT; not actual start or end times.
06:19– 06:57
Trip sto:62731676Vehicle position matchedFirst / last feed position: 6:07 a.m. EDT / 6:53 a.m. EDT; not actual start or end times.
06:20– 07:03
Trip sto:62731677Vehicle position matchedFirst / last feed position: 6:11 a.m. EDT / 7:01 a.m. EDT; not actual start or end times.
06:28– 07:06
Trip sto:62731678Vehicle position matchedFirst / last feed position: 6:30 a.m. EDT / 7:10 a.m. EDT; not actual start or end times.
06:28– 07:11
Trip sto:62732021Vehicle position matchedFirst / last feed position: 6:28 a.m. EDT / 7:13 a.m. EDT; not actual start or end times.
06:39– 07:22
Trip sto:62731681Vehicle position matchedFirst / last feed position: 6:39 a.m. EDT / 7:22 a.m. EDT; not actual start or end times.
06:42– 07:20
Trip sto:62731679Vehicle position matchedFirst / last feed position: 6:45 a.m. EDT / 7:23 a.m. EDT; not actual start or end times.
06:50– 07:35
Trip sto:62731682Vehicle position matchedFirst / last feed position: 6:52 a.m. EDT / 7:32 a.m. EDT; not actual start or end times.
06:50– 07:30
Trip sto:62732018Vehicle position matchedFirst / last feed position: 6:38 a.m. EDT / 7:30 a.m. EDT; not actual start or end times.
07:02– 07:48
Trip sto:62731684Vehicle position matchedFirst / last feed position: 7:01 a.m. EDT / 7:45 a.m. EDT; not actual start or end times.
07:02– 07:43
Trip sto:62731698Vehicle position matchedFirst / last feed position: 6:47 a.m. EDT / 7:38 a.m. EDT; not actual start or end times.

· Open all evidence for this day

Loading the route history. Live times above are ready to use.

Would you count on route 200?

No sign-in needed. A vote from a device that is not signed in counts a little less than one from an account, and a person who rates many routes counts a little less on each, so no one voice outweighs the rest.

Download evidence image

Evidence behind this pageOpen the definition, method, sources, dates, coverage, and known limits.

What is being shown

The current public route group, its published schedule variants and stop patterns, current operations, and reliability from matching eligible final provider predictions where available.

How it was produced

1 current GTFS route record variants are grouped by operator and public route number. Stop patterns remain tied to their published variant; aggregated reliability records are not merged into an invented percentile.

Collected or observed: October 8, 2026 at 2:39 a.m.
Computed or assembled: October 8, 2026 at 1:33 a.m.
Sample: 17,572 eligible settled provider predictions across 1 matching reliability records.
Coverage: 3 published stop patterns containing 46 stop calls are available on this page.
Method or data version: last-prediction-within-ten-minutes-v1; ca455c71-c30a-4e4d-8b72-2709212731cd; a7e1f22955084828484cca5e8f1ebff9e785c70984ad5dd93b872a5d64ace6e4

Sources

Limits to keep in mind

Schedule variants can apply on different dates. A grouped route is not a claim that every pattern operates today.
Accessibility fields report only what the operator publishes; an unknown value is not confirmation of access.

Suggest a factual correction

Rider evidence

Community reports

Signals below are moderated community aggregates, not official operator notices or reliability scores.

You can report without signing in. Anonymous reports count a little less when we calculate public patterns. You can add an account after submitting.

Report a specific problem

Emergency: call 9-1-1. Check official OC Transpo or STO notices before travelling.

Source: currently imported STO GTFS. Check the Alerts panel for current official notices and each stop page for observed departures.

Ride now

Route 200 right now

Where will you board?

Toward Lorrain · CENTRE RIDEAU to STATION LORRAIN arrêt d'arrivée

Toward Ottawa · STATION LORRAIN to CENTRE RIDEAU

Toward Ottawa · Station LABROSSE #1 to CENTRE RIDEAU

Stops and map

Explore the route

Where does it go?

CENTRE RIDEAU to STATION LORRAIN arrêt d'arrivée · 16 stops

Service records for this stop pattern

STATION LORRAIN to CENTRE RIDEAU · 16 stops

Service records for this stop pattern

Station LABROSSE #1 to CENTRE RIDEAU · 14 stops

Service records for this stop pattern

Performance

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

Cancellations on this route

Buses arriving bunched

City road work near this route

When this route is usually busy

What does the evidence show?

The hours we have evidence for

What about time of day?

What this route needs

Where and when did predictions differ repeatedly?

Check every trip and date

What riders want to know

Selected service day from each published schedule

Before

New schedule

Did service improve after the change?

Before

New schedule

How did predictions compare with the timetable?

Trips scheduled that day

Share this page

What is being shown

How it was produced

Evidence dates

Sources

Limits to keep in mind

Community reports

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

Cancellations on this route

Buses arriving bunched

City road work near this route

When this route is usually busy

What does the evidence show?

The hours we have evidence for

What about time of day?

What this route needs

Where and when did predictions differ repeatedly?

Check every trip and date

What riders want to know

Selected service day from each published schedule

Before

New schedule

Did service improve after the change?

Before

New schedule

How did predictions compare with the timetable?

Trips scheduled that day

What is being shown

How it was produced

Evidence dates

Sources

Limits to keep in mind