Skip to main content
Otranspo
FR

Route

90

OC Transpo

Greenboro ↔ Hurdman
All imported trips are marked accessible.Imported schedule valid through: Oct 4, 2026

Verdict

What this route needs

Nothing here crossed the thresholds this report uses, across 21 measured hours.

Arrivals within five minutes, by hour of day, last 14 days, 21 hours measured
  1. 00:00: 87.5% of arrivals on time, 526 arrivals, typically 0.5 min late
  2. 01:00: not enough data
  3. 02:00: not enough data
  4. 03:00: not enough data
  5. 04:00: not enough data
  6. 05:00: 97.7% of arrivals on time, 651 arrivals, typically 0.3 min late
  7. 06:00: 95.4% of arrivals on time, 1,400 arrivals, typically 1 min late
  8. 07:00: 78.9% of arrivals on time, 2,018 arrivals, typically 2.3 min late
  9. 08:00: 81.4% of arrivals on time, 1,413 arrivals, typically 1.6 min late
  10. 09:00: 89.4% of arrivals on time, 1,450 arrivals, typically 1.3 min late
  11. 10:00: 91.2% of arrivals on time, 1,307 arrivals, typically 0.9 min late
  12. 11:00: 91.9% of arrivals on time, 1,810 arrivals, typically 1.1 min late
  13. 12:00: 91.9% of arrivals on time, 1,497 arrivals, typically 0.8 min late
  14. 13:00: 86.5% of arrivals on time, 1,503 arrivals, typically 1.2 min late
  15. 14:00: 75.9% of arrivals on time, 1,388 arrivals, typically 1.7 min late
  16. 15:00: 76.1% of arrivals on time, 1,189 arrivals, typically 0.9 min late
  17. 16:00: 76.5% of arrivals on time, 1,168 arrivals, typically 1.6 min late
  18. 17:00: 74.3% of arrivals on time, 956 arrivals, typically 2 min late
  19. 18:00: 87.4% of arrivals on time, 913 arrivals, typically 1.1 min late
  20. 19:00: 88.4% of arrivals on time, 810 arrivals, typically 0.9 min late
  21. 20:00: 74.9% of arrivals on time, 693 arrivals, typically 1.5 min late
  22. 21:00: 75.2% of arrivals on time, 605 arrivals, typically 2 min late
  23. 22:00: 81.4% of arrivals on time, 784 arrivals, typically 1.9 min late
  24. 23:00: 81.8% of arrivals on time, 929 arrivals, typically 1.7 min late
  • 90% or more on time
  • 80 to 90% on time
  • under 80% on time
  • not enough data
Measurements

Route check

How route 90 is doing

A plain-language summary of the strongest evidence we have. We say when the data cannot answer a question.

Bottom line

Usually close to schedule in the period we measured.

85 in 100 arrivals were within 5 minutes of schedule · 39,627 arrivals checked

Confidence in this summary: High

Based on 39,627 arrivals over 19 weekdays, from Aug 8, 2026 to Sep 7, 2026.

Updated Sep 7, 2026, 11:34 p.m.

Where and when does it keep going wrong?

These are repeated patterns, not one bad day or an unverified rider report. They are measured the same way as the verdict above, over the same arrivals, but they are counted per stop rather than per hour, so the two lists need not match line for line.

No recurring problem time has cleared our evidence threshold yet.

No current official notice matches this route.

Problem places

We do not yet have enough route-by-stop history to name a recurring problem stop. Rider reports are used as leads, not proof.

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 7

Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.

Possible no-shows after checking feed gaps?
303 of 630 checked trips need a closer look

303 of 630 trips with enough public-feed evidence had no matching position over 7 days. 77 of 707 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.

How late does this route get?
The slowest 5 in 100 were more than about 10.4 min late

85 in 100 arrivals were within 5 minutes of schedule.

Do buses bunch or leave long gaps?
7.8 min average predicted wait

1.5 min beyond the scheduled wait, based on 240 arrivals at 16 high-frequency stops over 3 days.

Schedule change check

Fall schedule: before and after

This compares the official schedule that ended with the one that started August 30. Schedule changes are facts about what was planned; they do not prove that a trip ran.

Current published schedule began September 4, 2026

What the official notice says about this route

The City’s public summary did not name this route. The feed comparison below can still show a changed timetable, but it cannot tell us why it changed.

Read the official August 30 service-change notice →

One comparable weekday from each published schedule

We use 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.

Before

Service date checked: August 31, 2026

Scheduled trips
126
Distinct scheduled stops
118
Distinct published paths
5
Published service span
04:13–25:01

Feed fingerprint: ecc28a3727bcaff4 · 345fd07d-fb05-4eaa-8ec2-3daf8b7fcbe9

New schedule

Service date checked: September 7, 2026

Scheduled trips
66
Distinct scheduled stops
103
Distinct published paths
2
Published service span
07:03–23:40

Feed fingerprint: e0b417f2ea03fcf0 · 37ff8dfc-21cc-48c3-9eba-fc0d2e50b2ad

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.

Still collecting: before has 21,021 arrivals over 11 days; after has 3,178 arrivals over 3 days. No improvement or decline is claimed yet.

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: Regular all-stop route

We compare observed arrivals with the official schedule. A result needs at least 200 arrivals. 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
  1. Official current feed: explicit cancellations, skipped stops and active notices.
  2. Matched observations: vehicle positions and settled predictions tied to the official schedule.
  3. Official timetable: what was planned, kept separate from what was observed.
  4. Rider and operator reports: leads about routes, times and places to investigate, not numeric proof by themselves.

Would you count on route 90?

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.

Share this page

Use the permanent public link to this page and its sources.

Download evidence image

Only the canonical public link is shared. Panel state, location, receipts, and other browser-only details are left out. Email and social services apply their own privacy terms.

Live route map

Where the buses are now

Fresh vehicle positions appear on the route below. A marker stops moving when the evidence runs out. We do not invent movement.

Route and live buses

The line is the official route. Dots show published stops, buses seen now and stops named in current notices.

0 official shapes · 118 stops · 0 vehicle markers

Loading official route geometry · Loading current vehicles

Markers move between GPS fixes using measured progress along the published route. They pause after one measured reporting interval, on a measured standstill, or when evidence becomes stale.

Open the full-screen map →
Today’s schedule

Service date September 8, 2026

Towards Greenboro
60 scheduled trips
6:13 a.m.–1:01 a.m. (next day)
15 min median scheduled gap
Towards St Patricks
1 scheduled trip
7:44 a.m.–8:12 a.m.
Scheduled gap unavailable because fewer than two distinct trips start
Towards Greenboro Uplands
1 scheduled trip
2:42 p.m.–3:22 p.m.
Scheduled gap unavailable because fewer than two distinct trips start
Towards Hurdman
64 scheduled trips
4:13 a.m.–12:09 a.m. (next day)
15 min median scheduled gap

Span and median gap are computed from today’s official GTFS stop_times. They are timetable measures, not observed headways or a frequency guarantee.

Next trips from the ends of the route

These are trip starts. For the time at your stop, open that stop’s departure board.

  1. Towards Hurdman

    Starts at GREENBORO B

    Timetable only. No usable prediction is available for this trip.

    GREENBORO BOpen scheduled trip

  2. Towards Hurdman

    Starts at GREENBORO B

    Timetable only. No usable prediction is available for this trip.

    GREENBORO BOpen scheduled trip

  3. Towards Hurdman

    Starts at GREENBORO B

    Timetable only. No usable prediction is available for this trip.

    GREENBORO BOpen scheduled trip

  4. Towards Hurdman

    Starts at GREENBORO B

    Timetable only. No usable prediction is available for this trip.

    GREENBORO BOpen scheduled trip

Showing 4 of 7 trips. Open a stop for its full departure board.

Buses seen now

The current healthy operator position feed contains no vehicle matched to this route.

Official notices

No matching active notice appears in the current healthy operator feed.

Planned changes

No safely matched planned change is recorded for this route.

These are Otranspo register records, separate from operator alerts. A record is attached only when its route label identifies one operator; ambiguous OC Transpo/STO number matches are withheld.

Evidence checked Sep 8, 2:22 a.m.

Provisional results, published evidence

When is this route reliable?

Every hour below is backed by this route’s settled arrivals. “On time” means no more than five minutes early or late, so a bus that leaves very early counts as a failure for the waiting rider.

Evidence window: August 8, 2026 to September 7, 2026

Within 5 minutes of schedule
85.2%
Arrivals checked
39,627
Weekdays with data
19
How late the worst 5 in 100 were
10.4 min late
Patterns by hour (21)
HourOn timeMedianWorst 5 in 100Evidence
00:0087.5%0.5 min late7.9 min late526 · 6 days
04:00100.0%0.5 min late2.2 min late196 · 4 days
05:0097.7%0.3 min late4.4 min late651 · 6 days
06:0095.4%1 min late4.8 min late1,400 · 6 days
07:0078.9%2.3 min late8.2 min late2,018 · 6 days
08:0081.4%1.6 min late7.1 min late1,413 · 7 days
09:0089.4%1.3 min late9.8 min late1,450 · 9 days
10:0091.2%0.9 min late5.4 min late1,307 · 8 days
11:0091.9%1.1 min late5.6 min late1,810 · 8 days
12:0091.9%0.8 min late5.5 min late1,497 · 9 days
13:0086.5%1.2 min late7.6 min late1,503 · 8 days
14:0075.9%1.7 min late17 min late1,388 · 7 days
15:0076.1%0.9 min late12.8 min late1,189 · 8 days
16:0076.5%1.6 min late8.4 min late1,168 · 8 days
17:0074.3%2 min late10.8 min late956 · 8 days
18:0087.4%1.1 min late7.4 min late913 · 7 days
19:0088.4%0.9 min late6.5 min late810 · 8 days
20:0074.9%1.5 min late8.2 min late693 · 8 days
21:0075.2%2 min late10.2 min late605 · 6 days
22:0081.4%1.9 min late6.8 min late784 · 7 days
23:0081.8%1.7 min late16.2 min late929 · 8 days

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

Scheduled bus, but not observed in realtime

327 / 641 scheduled trips published at least one position across 4 service days (51.0%).

  • 14:0031 / 40 trips without a position22.5%
  • 23:0013 / 21 trips without a position38.1%
  • 20:0014 / 24 trips without a position41.7%
  • 16:0022 / 40 trips without a position45.0%
  • 17:0019 / 36 trips without a position47.2%
  • 10:0021 / 40 trips without a position47.5%

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.

Arrival check: the last prediction within ten minutes of arrival, counted once per trip, stop and service date. Trip 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.

See all stops and route patterns

Stops and stations

5 official stop patterns

Each row below is one exact stop order published in the official schedule. Short turns and alternate destinations stay separate.

Choose a direction or stop pattern
Clear selection

  • Towards Greenboro: HURDMAN D to GREENBORO C

    53 stops · 533 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

    Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday

    12 official service records

    3 added dates and 23 removed dates

    View stops and calendar →

  • Towards St Patricks: UPLANDS / BOWESVILLE to HERON / ST-PATS H.S

    29 stops · 5 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

    Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

  • Towards Greenboro Uplands: ST PATS HS to UPLANDS / BOWESVILLE

    35 stops · 5 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

    Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

  • Towards Hurdman: GREENBORO B to HURDMAN B

    50 stops · 554 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

    Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday

    12 official service records

    3 added dates and 23 removed dates

    View stops and calendar →

  • Towards Hurdman: FLANNERY / BROOKFIELD H.S. to HURDMAN B

    14 stops · 5 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

    Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

Official feed version 37ff8dfc-21cc-48c3-9eba-fc0d2e50b2ad

Source checksum e0b417f2ea03fcf035ed795c07b47461157b81b0c43d43639094105ed66b0a4a

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 matching observed reliability 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.

Evidence dates

Collected or observed
Computed or assembled
Sample
39,627 settled arrivals across 1 matching reliability records.
Coverage
5 published stop patterns containing 181 stop calls are available on this page.
Method or data version
last-prediction-within-ten-minutes-v1; 37ff8dfc-21cc-48c3-9eba-fc0d2e50b2ad; e0b417f2ea03fcf035ed795c07b47461157b81b0c43d43639094105ed66b0a4a

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 OC Transpo GTFS. Check the Alerts panel for current official notices and each stop page for observed departures.