Skip to main content
Otranspo

OC Transpo · feed ID 2233

Route 58 · destination not published

Observed 94 seconds ago · Sep 19, 2026, 4:48 p.m.

This report separates current operator-published facts from historical measures the present schema cannot attribute to a stable physical bus.

Current assignment

Route
No schedule-validated route assignment
Destination
Destination unavailable
Direction
Direction 0
Observation age
94 seconds
Last observed
Sep 19, 2026, 4:48 p.m.
Operator
OC Transpo
Position method
observed
Feed identifier
2233
Physical identity status
Unverified because no physical-fleet registry has been reviewed

Operator GTFS-RT vehicle position · current-vehicle-snapshot-v1 · One current snapshot; observations older than 180 seconds are excluded.

Upcoming matched stops

Ordered stops published for this vehicle’s current trip update. A prediction is shown only when the operator supplied one.

The current feed does not publish enough trip-stop information to name an upcoming stop.

Share this page

Share this page

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

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.

A verified evidence image is not available for this page. The public link and image description remain available.

30-day feed-ID history

This ledger shows where this public feed ID was observed on scheduled trips. It can expose a recurring visibility pattern, but it cannot prove whether a gap came from an operator action, onboard equipment, communications, or another data problem.

19
Observed trips
3
Service dates
8
Routes
Service dateRouteTripFirst / last observed
2026-09-195813013110Sep 19, 2026, 4:07 p.m. / Sep 19, 2026, 4:48 p.m.
2026-09-19586498110Sep 19, 2026, 3:45 p.m. / Sep 19, 2026, 4:05 p.m.
2026-09-195815618110Sep 19, 2026, 3:06 p.m. / Sep 19, 2026, 3:43 p.m.
2026-09-195814607110Sep 19, 2026, 2:31 p.m. / Sep 19, 2026, 3:05 p.m.
2026-09-19186919110Sep 19, 2026, 1:26 p.m. / Sep 19, 2026, 2:30 p.m.
2026-09-191815986110Sep 19, 2026, 12:23 p.m. / Sep 19, 2026, 1:25 p.m.
2026-09-182013214100Sep 18, 2026, 10:06 a.m. / Sep 18, 2026, 11:06 a.m.
2026-09-182018397100Sep 18, 2026, 8:53 a.m. / Sep 18, 2026, 10:05 a.m.
2026-09-18324063100Sep 18, 2026, 7:57 a.m. / Sep 18, 2026, 8:52 a.m.
2026-09-182410105100Sep 18, 2026, 6:44 a.m. / Sep 18, 2026, 7:55 a.m.
2026-09-1710521715110Sep 18, 2026, 2:05 a.m. / Sep 18, 2026, 2:50 a.m.
2026-09-171052467110Sep 18, 2026, 12:58 a.m. / Sep 18, 2026, 2:04 a.m.
2026-09-179815208110Sep 17, 2026, 11:27 p.m. / Sep 18, 2026, 12:56 a.m.
2026-09-17434317110Sep 17, 2026, 11:21 p.m. / Sep 17, 2026, 11:44 p.m.
2026-09-174310071110Sep 17, 2026, 10:19 p.m. / Sep 17, 2026, 11:20 p.m.
2026-09-174318699110Sep 17, 2026, 10:31 p.m. / Sep 17, 2026, 11:02 p.m.
2026-09-17436297110Sep 17, 2026, 9:23 p.m. / Sep 17, 2026, 10:18 p.m.
2026-09-17437276110Sep 17, 2026, 8:50 p.m. / Sep 17, 2026, 10:00 p.m.
2026-09-17435414110Sep 17, 2026, 8:33 p.m. / Sep 17, 2026, 9:22 p.m.

Measures and evidence

Every row states its source, method, window, sample, and freshness. Missing evidence remains unavailable.

Current speed

0 km/h

Source
Operator GTFS-RT vehicle position
Method
Published speed field with its presence flag; absent fields are not decoded as zero.
Window
One current snapshot; observations older than 180 seconds are excluded.
Sample
1 current vehicle observation
Freshness
Sep 19, 2026, 4:48 p.m.

Operator-published occupancy

Unavailable. This does not mean zero.

Source
Operator GTFS-RT vehicle position
Method
Published GTFS-RT occupancy enum; absent occupancy is not decoded as EMPTY.
Window
One current snapshot; observations older than 180 seconds are excluded.
Sample
Unavailable
Freshness
Sep 19, 2026, 4:48 p.m.

Historical reliability by physical bus

Unavailable. This does not mean zero.

Source
Otranspo settled-arrival archive
Method
Unavailable: settled arrivals do not retain a vehicle identifier and the feed identifier is not a verified physical identity.
Window
Unavailable
Sample
Unavailable
Freshness
Unavailable

Rider-reported crowding by physical bus

Unavailable. This does not mean zero.

Source
Privacy-thresholded rider observations
Method
Unavailable: public cohorts are grouped by route after five distinct accounts qualify; no physical-vehicle cohort is published.
Window
Unavailable
Sample
Unavailable
Freshness
Unavailable
Evidence behind this pageOpen the definition, method, sources, dates, coverage, and known limits.

What is being shown

One current operator-feed vehicle observation. The feed identifier is not treated as a verified physical fleet identity.

How it was produced

current-vehicle-snapshot-v1 keeps observations no older than 180 seconds and preserves missing speed or occupancy as unavailable.

Evidence dates

Collected or observed
Computed or assembled
Sample
This selected observation is part of a current snapshot containing 402 usable vehicle observations.
Method or data version
public-feed-id-trip-history-v1

Sources

Limits to keep in mind

  • The operator feed identifier is not linked to a reviewed physical-fleet registry.
  • Settled reliability observations do not retain a physical vehicle identifier, so they cannot support a bus reliability ranking.
  • Current rider crowding evidence does not support a privacy-safe physical-bus ranking.
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.

Report crowding near this vehicle

The report flow rechecks that the live vehicle is still nearby and fresh before accepting an observation.

Report crowding near this vehicle