Vehicle-door sensors collect boardings and alightings for software review against routes, trips and stops. Transit planners validate the returned counts and use the resulting ridership records to review demand and service.
Matching passenger counts to the service actually run gives transit planners a record for reviewing demand across routes and stops. ETA Transit connects compatible automatic passenger counters with service context and Tally review tools. Teams use the resulting records for ridership analysis, internal reports and selected reporting preparation.
Sensors at the vehicle doors collect boarding and alighting activity. Compatible onboard systems return count records with the corresponding route, trip, stop, schedule and time. The installation can use supported existing counters or a selected new sensor set, with the available onboard interfaces and service data linked into the project. Where supported, manual or mobile-terminal backup counting adds records when automated inputs require review or are unavailable.
Staff examine the returned data in Tally, identify missing values or exceptions and resolve issues before finalizing reports. Validated records show activity by route, direction, trip, time period or individual stop. Planning teams compare changing demand and prepare service-frequency or route-productivity reviews using the represented counts. Selected load information also supplies an input for operating decisions and rider communication. The workflow carries physical door counts into human data checks and reusable ridership records, giving the agency a consistent basis for its service review.

Sensors, gateways and spare units
Site survey, mounting, commissioning and configuration
Platform subscription, connectivity, data and support
This is an estimate by IoT Apps based on comparable deployments, not a quote from ETA Transit.
Get an estimate for your own project and invite ETA Transit to confirm a price and lead time, on this page. Taxes, shipping, civil works and custom integration are not included. How IoT Apps estimates costs


Count transit boardings and exits for load reports.

Count transit boardings and exits for route planning.


Compatible sensors count boardings and alightings at the equipped vehicle doors, with records linked to the represented service.
The workflow associates counts with route, trip, stop, schedule and time so the agency can relate passenger activity to the service actually run.
The project reviews existing equipment and interfaces for compatibility, then selects integration or replacement for the represented service.
Staff use its review and validation workflow to identify missing data, resolve exceptions and prepare the accepted passenger records for the selected reporting process.
Every page carries a cost estimate by IoT Apps for your own sites and assets; set your budget and invite ETA Transit to confirm a price and lead time.
For 1 site with 10 monitored assets in United States, IoT Apps estimates $1,900 – $6,000 in the first year and $300 – $1,000 every year after. This is an estimate based on comparable deployments, not a quote from ETA Transit.

Ask the AI Solution Architect: compare this solution against alternatives, check connectivity for your region and get integration guidance. Included with IoT Apps Enterprise.
Ask the Architect