Skip to main content
Otranspo

Current feed observation · not a verified fleet record

Feed vehicle sto:2024

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

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.

This feed ID is not in the current live snapshot. Its retained history remains available instead of disappearing.

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.

33
Observed trips
4
Service dates
15
Routes
Service dateRouteTripFirst / last observed
2026-09-1255sto:62698247Sep 13, 2026, 12:18 a.m. / Sep 13, 2026, 1:02 a.m.
2026-09-12400sto:62698209Sep 12, 2026, 11:05 p.m. / Sep 12, 2026, 11:55 p.m.
2026-09-12400sto:62698232Sep 12, 2026, 10:19 p.m. / Sep 12, 2026, 11:03 p.m.
2026-09-12400sto:62698067Sep 12, 2026, 9:12 p.m. / Sep 12, 2026, 9:57 p.m.
2026-09-1238sto:62698009Sep 12, 2026, 7:28 p.m. / Sep 12, 2026, 8:03 p.m.
2026-09-1238sto:62697977Sep 12, 2026, 6:34 p.m. / Sep 12, 2026, 7:11 p.m.
2026-09-1238sto:62697927Sep 12, 2026, 5:44 p.m. / Sep 12, 2026, 6:33 p.m.
2026-09-1238sto:62697874Sep 12, 2026, 5:01 p.m. / Sep 12, 2026, 5:39 p.m.
2026-09-12371sto:62697727Sep 12, 2026, 2:39 p.m. / Sep 12, 2026, 3:24 p.m.
2026-09-1237sto:62697523Sep 12, 2026, 1:29 p.m. / Sep 12, 2026, 2:26 p.m.
2026-09-1233sto:62698293Sep 12, 2026, 12:32 p.m. / Sep 12, 2026, 1:17 p.m.
2026-09-1231sto:62698256Sep 12, 2026, 11:36 a.m. / Sep 12, 2026, 12:24 p.m.
2026-09-1249sto:62697286Sep 12, 2026, 8:59 a.m. / Sep 12, 2026, 9:55 a.m.
2026-09-1249sto:62697365Sep 12, 2026, 7:53 a.m. / Sep 12, 2026, 8:59 a.m.
2026-09-1249sto:62697366Sep 12, 2026, 7:04 a.m. / Sep 12, 2026, 7:52 a.m.
2026-09-11800sto:62732542Sep 11, 2026, 3:30 p.m. / Sep 11, 2026, 4:42 p.m.
2026-09-11400sto:62731707Sep 11, 2026, 2:40 p.m. / Sep 11, 2026, 3:29 p.m.
2026-09-1135sto:62730620Sep 11, 2026, 9:43 a.m. / Sep 11, 2026, 10:26 a.m.
2026-09-1135sto:62730619Sep 11, 2026, 8:49 a.m. / Sep 11, 2026, 9:41 a.m.
2026-09-1149sto:62731319Sep 11, 2026, 8:09 a.m. / Sep 11, 2026, 8:47 a.m.
2026-09-1127sto:62731804Sep 11, 2026, 6:43 a.m. / Sep 11, 2026, 7:31 a.m.
2026-09-1059sto:62731094Sep 10, 2026, 10:40 p.m. / Sep 10, 2026, 11:23 p.m.
2026-09-1059sto:62731101Sep 10, 2026, 9:30 p.m. / Sep 10, 2026, 10:23 p.m.
2026-09-1059sto:62730936Sep 10, 2026, 8:38 p.m. / Sep 10, 2026, 9:29 p.m.
2026-09-1038sto:62731141Sep 10, 2026, 7:06 p.m. / Sep 10, 2026, 8:23 p.m.
2026-09-1033sto:62730631Sep 10, 2026, 6:17 p.m. / Sep 10, 2026, 7:06 p.m.
2026-09-1031sto:62731477Sep 10, 2026, 5:23 p.m. / Sep 10, 2026, 6:10 p.m.
2026-09-1031sto:62730916Sep 10, 2026, 4:23 p.m. / Sep 10, 2026, 5:22 p.m.
2026-09-1033sto:62731294Sep 10, 2026, 3:21 p.m. / Sep 10, 2026, 4:21 p.m.
2026-09-0478sto:62731648Sep 4, 2026, 9:22 a.m. / Sep 4, 2026, 9:59 a.m.
2026-09-0472sto:62732375Sep 4, 2026, 8:47 a.m. / Sep 4, 2026, 9:15 a.m.
2026-09-0472sto:62732385Sep 4, 2026, 8:34 a.m. / Sep 4, 2026, 8:46 a.m.
2026-09-04826sto:62731921Sep 4, 2026, 7:30 a.m. / Sep 4, 2026, 8:06 a.m.
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
33 retained observed trips
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

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