Transport for NSW reports that every contracted bus in rural and regional New South Wales now carries GPS and automatic passenger counting equipment: 3,010 buses, more than 3,880 routes and around 316,000 kilometres a day (Transport for NSW media release, 3 July 2025). The Transport Connected Bus (TCB) programme is a useful case for any authority or operator planning real-time information across many small contractors. The hard part is rarely the tracking itself, it is keeping one data contract across 451 operators.
What did NSW actually deploy in regional bus real-time?
According to Transport for NSW's release of 3 July 2025, the programme brought regional NSW in line with Greater Sydney and the Outer Metropolitan areas, and the vehicle fit-outs were completed ahead of schedule. The scope covers regular and school services. Passengers can follow buses in real time in any travel app, including Opal Travel, or in the Transport for NSW Trip Planner website, with arrival times, capacity information, interactive maps and digital timetables.
The figures published in the release give a sense of scale:
- 3,010 contracted buses fitted with GPS and automatic passenger counting.
- More than 3,880 routes.
- Around 316,000 kilometres travelled per day.
- 451 contracted bus operators, from large fleet companies to small mum-and-dad businesses.
The Transport Connected Bus portal describes the operator side: every bus is fitted with a Driver Console, and operators manage their fleet with a Windows-based application called Traffic Studio. The release does not name hardware or software suppliers, and this article does not either.
An earlier Transport for NSW release, dated 4 October 2023, gives the trajectory. It reported that the first two phases fitted 283 and 921 vehicles, that around 1,800 more buses were to follow in a third phase, and that more than 1.5 million trips had been tracked across the state since July 2020. Between that release and the July 2025 one, the programme reached every regional contract.
Why does having 451 operators change the data problem?
The release describes operators "ranging from large fleet companies to small mum-and-dad businesses". In a market like this, data quality depends less on technology than on process. Many small fleets mean many people who install, test, correct and support the equipment, and many vehicles that change contract, route or timetable during the year.
A 2021 post on the Transport for NSW Open Data forum, announcing real-time data for two additional regions (Armidale and Bathurst), shows what that looks like in practice. It lists eleven agency entries for those two regions alone, and some operator names appear under two identifiers. Operator identities, contract references and agency IDs in a feed behave like master data: if they drift, every downstream app inherits the confusion.
The TCB portal answers this with a standard operator journey that runs from an information session and vehicle installation through route data capture to go-live and a three-week transition. It also provides training packages and a self-service portal, called OT Connect, where operators log and track TCB-related issues. The lesson is organisational: a repeatable onboarding path and a single place to raise faults are what make hundreds of go-lives manageable.
How does the data reach passengers and developers?
Transport for NSW publishes regional bus data through its API gateway. The 2021 forum post lists, for each region, a GTFS timetable feed, a trip updates feed and a vehicle position feed under region-specific paths. The open data portal dataset "Public Transport - Realtime Vehicle Positions" describes current vehicle positions in GTFS Realtime format for buses, ferries, light rail, NSW Trains, Metro and regional bus services, under a Creative Commons Attribution licence. The dataset page also notes that regional services are sometimes referred to as TCB.
Two consequences follow for any operator working in a similar environment:
- The same open feed format serves every mode, so regional operators appear in the same apps as the capital's networks.
- Third parties, not only the authority's own journey planner, read the feed. Errors are therefore visible to people the operator never chose as partners.
What can go wrong when many small fleets feed one network?
The NSW sources do not describe individual faults, so the points below are general operating practice, not claims about NSW. They are the checks that matter in any contracted regional network.
- Trip matching. A vehicle position is only useful when the vehicle is paired with the right trip. A wrong pairing produces confident but wrong arrival times. Our article on how an AVM keeps every vehicle paired to the right service covers the mechanics.
- School services. The release states that school services are included. School timetables follow term calendars, so calendar exceptions need to be maintained as carefully as the base timetable.
- Cancellations. The release notes that operators on the NSW North Coast used the technology to cancel trips promptly and consistently during ex-Tropical Cyclone Alfred. A feed that carries cancellations is worth more to passengers than one that only shows moving buses.
- Capacity information. Passenger load shown in an app is only as good as the counting data behind it and the way it is published.
- Silent vehicles. When a bus stops reporting, someone has to notice, and someone has to fix it. The OT Connect model above is one answer.
Which Pysae modules address these problems?
The modules below are described on the Pysae platform page. We list only what the page states.
Pysae Operations gives a live map with delays, advances and regularity per line calculated automatically, alerts and incidents with immediate escalation, and automatic GTFS-RT, SIRI and ITxPT exports to regional calculators and transport authorities. That is the layer that turns raw positions into a feed an authority can consume.
Pysae Fleet delivers a pre-configured onboard box wired to the vehicle's CAN/FMS bus, with a live map, speed and trip history transmitted continuously and no driver action required. Punctuality, mileage and journey time reports are generated automatically from field data.
Pysae Network handles the timetable side: calendars and exceptions such as back-to-school, summer timetables and public holidays, with certified GTFS and NeTEx exports to regional journey planners. For school-heavy regional networks, that is where term-time changes should be entered once and reused.
What should an authority or operator take from the NSW programme?
First, define the data contract before choosing hardware: which feeds, which identifiers, which fields, and who is responsible when something is wrong. Second, standardise onboarding so that the thousandth go-live looks like the tenth. Third, monitor feed health as an operational task, not as an IT project: a bus that silently stops reporting is a service problem.
None of this depends on the size of the operator. A family business with a handful of vehicles needs the same trip pairing, the same calendar discipline and the same fault path as a large fleet. A platform that publishes standard feeds makes it easier for authorities to extend real-time information to every contract.
To see how Operations, Fleet and Network work together to publish a reliable GTFS-RT feed across a mixed network, use the "Request a demo" button on this page.
Frequently asked questions
How many buses does the NSW Transport Connected Bus programme cover?
Transport for NSW's release of 3 July 2025 reports 3,010 contracted buses in rural and regional NSW, on more than 3,880 routes, travelling around 316,000 kilometres per day.
Does regional NSW bus data use an open standard?
Transport for NSW publishes regional bus timetables, trip updates and vehicle positions through its API gateway, and its open data portal describes vehicle positions in GTFS Realtime format, including regional bus services, under a Creative Commons Attribution licence.
How many operators are involved?
The release counts 451 contracted bus operators, from large fleet companies to small mum-and-dad businesses.
What does an AVM need to publish a reliable GTFS-RT feed?
At minimum: each vehicle paired to the right trip, calendars and exceptions that match the timetable, cancellations carried into the feed, and a way to detect vehicles that stop reporting.
Which Pysae modules relate to real-time bus data?
Pysae Operations exports GTFS-RT, SIRI and ITxPT, Pysae Fleet provides the onboard box and live vehicle data, and Pysae Network manages calendars, exceptions and GTFS and NeTEx exports.