Skip to main content
Otranspo

Current feed observation · not a verified fleet record

Feed vehicle 4857

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.

38
Observed trips
4
Service dates
13
Routes
Service dateRouteTripFirst / last observed
2026-09-138021129010Sep 13, 2026, 7:46 p.m. / Sep 13, 2026, 8:34 p.m.
2026-09-138022506010Sep 13, 2026, 6:39 p.m. / Sep 13, 2026, 7:44 p.m.
2026-09-135122586010Sep 13, 2026, 4:35 p.m. / Sep 13, 2026, 6:38 p.m.
2026-09-13519002010Sep 13, 2026, 3:46 p.m. / Sep 13, 2026, 4:34 p.m.
2026-09-138613141010Sep 13, 2026, 2:04 p.m. / Sep 13, 2026, 3:44 p.m.
2026-09-138610156010Sep 13, 2026, 1:47 p.m. / Sep 13, 2026, 2:43 p.m.
2026-09-136811480010Sep 13, 2026, 12:31 p.m. / Sep 13, 2026, 1:46 p.m.
2026-09-136810018010Sep 13, 2026, 11:20 a.m. / Sep 13, 2026, 12:29 p.m.
2026-09-126210431070Sep 12, 2026, 5:57 p.m. / Sep 12, 2026, 7:12 p.m.
2026-09-12639915070Sep 12, 2026, 4:50 p.m. / Sep 12, 2026, 5:56 p.m.
2026-09-12633134070Sep 12, 2026, 2:57 p.m. / Sep 12, 2026, 4:48 p.m.
2026-09-12616603070Sep 12, 2026, 2:01 p.m. / Sep 12, 2026, 3:24 p.m.
2026-09-12613923070Sep 12, 2026, 12:16 p.m. / Sep 12, 2026, 1:59 p.m.
2026-09-12623734070Sep 12, 2026, 10:50 a.m. / Sep 12, 2026, 12:15 p.m.
2026-09-12625916070Sep 12, 2026, 8:28 a.m. / Sep 12, 2026, 10:48 a.m.
2026-09-12627611070Sep 12, 2026, 6:42 a.m. / Sep 12, 2026, 8:27 a.m.
2026-09-118622229060Sep 11, 2026, 11:16 p.m. / Sep 11, 2026, 11:52 p.m.
2026-09-118616632060Sep 11, 2026, 10:58 p.m. / Sep 11, 2026, 11:15 p.m.
2026-09-118618160060Sep 11, 2026, 9:48 p.m. / Sep 11, 2026, 10:57 p.m.
2026-09-1186924060Sep 11, 2026, 9:28 p.m. / Sep 11, 2026, 9:47 p.m.
2026-09-116223197060Sep 11, 2026, 8:10 p.m. / Sep 11, 2026, 9:26 p.m.
2026-09-11667148060Sep 11, 2026, 6:05 p.m. / Sep 11, 2026, 8:08 p.m.
2026-09-1111011262060Sep 11, 2026, 4:08 p.m. / Sep 11, 2026, 6:06 p.m.
2026-09-119311261060Sep 11, 2026, 3:54 p.m. / Sep 11, 2026, 4:06 p.m.
2026-09-11936670060Sep 11, 2026, 3:28 p.m. / Sep 11, 2026, 3:52 p.m.
2026-09-119323165060Sep 11, 2026, 3:14 p.m. / Sep 11, 2026, 3:26 p.m.
2026-09-119315977060Sep 11, 2026, 2:51 p.m. / Sep 11, 2026, 3:12 p.m.
2026-09-119319906060Sep 11, 2026, 1:33 p.m. / Sep 11, 2026, 2:51 p.m.
2026-09-119320038060Sep 11, 2026, 1:50 p.m. / Sep 11, 2026, 2:13 p.m.
2026-09-041419060060Sep 4, 2026, 5:12 p.m. / Sep 4, 2026, 6:10 p.m.
2026-09-041421660060Sep 4, 2026, 2:57 p.m. / Sep 4, 2026, 5:10 p.m.
2026-09-04673046060Sep 4, 2026, 2:08 p.m. / Sep 4, 2026, 2:51 p.m.
2026-09-04879412060Sep 4, 2026, 8:23 a.m. / Sep 4, 2026, 8:51 a.m.
2026-09-048728726060Sep 4, 2026, 7:51 a.m. / Sep 4, 2026, 8:22 a.m.
2026-09-048714678060Sep 4, 2026, 7:25 a.m. / Sep 4, 2026, 7:50 a.m.
2026-09-04878908060Sep 4, 2026, 6:20 a.m. / Sep 4, 2026, 7:24 a.m.
2026-09-048720280060Sep 4, 2026, 6:52 a.m. / Sep 4, 2026, 6:58 a.m.
2026-09-048720430060Sep 4, 2026, 6:13 a.m. / Sep 4, 2026, 6:49 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
38 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