SafePassengerEvery passenger counted.
Every stop called.
SafePassenger puts a counting-and-safety unit on each coach, then turns what it sees into the two things an operator can act on: who is actually on board, and what went wrong on the way.
Five fares nobody sold — counted at the door, not on the manifest
The count comes from the doorway, not the chart.
A camera over each door records every boarding and alighting, with a GPS fix and a timestamp on each one. The device streams those events up as they happen, so a trip's occupancy is known while the coach is still moving — and reconciled against the reservations your ticketing system already holds.
Per door, per stop
Boardings and alightings are attributed to the stop they happened at, so a short halt in the wrong place doesn't quietly become a scheduled one.
Booked against boarded
Reservations pulled from your ITS or Bitla system become the expected count. Every passenger counted above it is an unscheduled boarding — a fare that was collected, but not sold.
Flagged, not buried
Readings that can't be right — a count with no GPS lock, a door event out of sequence — are raised as anomalies rather than folded into the total.
A night run, reconstructed from the telemetry.
GPS pings, door states and counts arrive as a stream of raw points. The tracking pipeline clusters them into what actually happened: where the coach stopped, for how long, whether that halt was the scheduled stop, a dinner break, a restroom pause — or something nobody scheduled.
Break or detour
Dinner and restroom halts are classified by duration and position, so an unscheduled boarding stands out instead of hiding among legitimate stops.
Opened where, and when
Every door open is recorded with the position it happened at — including the ones that happen between stops, at speed.
Cloud verification
When a count needs confirming, the clip behind it is analysed on a cloud instance and the trip's numbers are corrected from the video.
The one person nobody on board is watching is the driver.
A second camera faces the cab. When the driver's eyes stay closed, the head drops, or the face leaves the frame, the unit records the seconds around it and uploads the clip — so a drowsy instance is footage you can watch, not a number in a report.
Clip, coach, timestamp
Each instance is filed under the bus and the date it happened on, ready to review the next morning — or while the coach is still running.
Mailed the same day
Drowsy instances go to the people you nominate: which bus, how many, which date, and a link straight through to the footage.
A covered lens is an event
If the camera is blocked, turned away or unplugged, that is recorded as its own event. A safety check nobody can switch off quietly.
Driver monitoring is a switch of its own — run it on the coaches you want it on, with counting on or off. The unit also uploads its own diagnostic clips, so you find out the camera has drifted before an incident does.
The stop announces itself, in the language of the route.
Every station on your network gets a recorded announcement in the voice and languages you choose. As the coach comes within the stop's radius, the unit plays it — welcome notes at the start, break announcements at a halt, the station name before each drop-off — and logs that it played, with the position it played at.
Announcement audio is generated per operator, per voice — add a station and its announcement is recorded for you, in every language that route runs in.
One screen, per trip, that tells you where the money went.
Trips roll up per stop and per city: what was booked, what boarded, how long the coach sat there. The rows that need a human are marked as such — a boarding at an unscheduled halt is not a rounding error, it is revenue leaving through the door.
| Stop | Reached | Halt | Booked | Boarded | On board | Status |
|---|---|---|---|---|---|---|
| Hubballi · Gokul Road | 20:05 | 12m | 14 | 14 | 14 | Matched |
| Dharwad · Jubilee Circle | 20:41 | 6m | 9 | 9 | 23 | Matched |
| NH-48 · km 412 | 21:58 | 4m | — | 5 | 28 | Unscheduled boarding |
| Belagavi · Dinner halt | 23:20 | 28m | — | 0 | 28 | Dinner break |
| Kolhapur · Bus Stand | 01:47 | 8m | 8 | 6 | 34 | 2 no-shows |
Illustrative trip — the figures above are a sample, not a customer's data.
What it takes to put this on a fleet.
- On the coach
- One edge unit per bus with a camera at each door. It buffers locally when the network drops and uploads when it returns — a coach out of coverage for an hour loses nothing.
- Your ticketing
- Reservations are pulled from the operator system you already run — ITS and Bitla are supported today — so nobody re-keys a manifest.
- Per-operator setup
- Routes, stops, schedules and announcement voices are configured once per company, then apply to every bus on the fleet.
- Reaching you
- Alerts go to the people you nominate, per product; trip and cost reports are emailed on a schedule you set.
- Turning it on
- Counting, drowsiness detection and announcements are separate switches. Start with one coach and one product.
Put it on one coach for a fortnight.
Pick a route you already suspect. We fit a single unit, you watch the trips come in, and at the end you have the count from the door to set against the count on the chart.
Defence Colony, Indiranagar,
Bengaluru, Karnataka 560038, India