Real-time bus tracking in Malta rests on GPS positions that each Malta Public Transport bus sends roughly every 5 seconds, according to the operator's own tracking page. Passengers read the result in the tallinja app, through a QR code at the stop and by SMS, and a digital signage system announced on 7 May 2026 covers six transport hubs. The same page lists the limits: a diverted route can hide a bus, and weak mobile coverage slows updates. For any operator, the lesson is that a tracking feature is only as good as the data discipline behind it.
How does real-time bus tracking work in Malta?
Malta Public Transport (MPT) explains the mechanics on its real-time bus tracking page. Each bus reports its position by GPS, and the page states that "the bus transmits its location approximately every 5 seconds via GPS." The estimated arrival time is, in the page's words, "based on real-time data, considering the bus's speed and other parameters." Passengers can open the "Track the Bus" feature in the app to see the journey of a bus towards their stop.
The idea is not new. In an announcement dated 26 April 2016, MPT launched the free tallinja app and described the same principle: every bus transmits its current location to a central system, which compares it with the planned position to estimate arrivals at about 2,000 stops. That announcement says customers could see the estimated arrival of buses reaching a stop within the next 30 minutes.
Two details from this description matter for anyone who buys or runs an AVM. First, an arrival estimate is a comparison between a live position and a planned position, so it depends on two data sets, not one. Second, freshness is visible to the passenger: MPT's page says that if the app does not receive the latest GPS location within 1 minute, the bus icon will grey out.
Which channels carry the same bus data to passengers?
The tracking page names three ways to read the data: the tallinja app, a QR code displayed on the bus stop timesheet, and an SMS sent to 5061 1010 with the bus stop code. On 7 May 2026, MPT announced a new digital signage system in six locations: Valletta Terminal, Malta International Airport, Marsa Park & Ride, Rabat Interchange, the University of Malta and Mġarr Harbour in Gozo. The announcement says the panels show "real-time updates for bus departures and service information."
The announcement also describes how the screens are fed: updates are delivered over high-speed internet connections and are "managed centrally" so that all information remains consistent across the network. It adds that the same real-time information is available in the tallinja app and through the QR codes on every bus stop schedule. The project was part-financed by the EU through NextGenerationEU funds, under the "Digitalise your Large Business Grant Scheme."
This is a useful model of how a modern network behaves: several channels show the same real-time information, and the screens are managed centrally. When a channel shows a different arrival time from another, passengers stop trusting all of them. The practical requirement for the AVM is therefore not to build more channels, but to publish one consistent feed that every channel consumes.
What happens to real-time data when a route is diverted?
MPT is open about the weak point. Its tracking page states that "bus visibility may be affected if a route is diverted or altered unexpectedly." It also warns that "poor cellular network coverage may affect the update frequency," and that offline use is not supported.
The diversion case deserves attention because it is where planned data and live data drift apart. A bus that leaves its planned path is still sending GPS positions, but the comparison with the planned position no longer holds unless the diversion is also recorded in the planned data. Whether a given system loses the bus entirely or shows a wrong estimate depends on how the diversion is entered, and MPT's page describes the visible result rather than the cause.
For operators, the fix is organisational as much as technical. The person who decides on a diversion in the control room needs one place to record it, and that record has to reach the app, the stop screens and the driver at the same time. Our article on GTFS-RT in practice: from GPS to the passenger's screen explains how real-time passenger information works. Our article on managing bus detours with trip modifications and GTFS covers how a detour can be described in the data feeds.
Why does a growing network make the data harder to keep right?
According to a Transport Ministry spokesperson quoted by MaltaToday, bus passenger trips "increased by 17.58% in May 2026, compared to May 2024," and the number of buses in circulation "rose by 22.65%" over the same period. The article, which is not dated on the page but refers to schedule changes on 13 June 2026 and 5 July 2026, reports that route 212 between Sliema and Buġibba, running every 20 minutes on weekdays, would move to every 15 minutes from 5 July, and that route 53 between Valletta and Rabat runs every 30 minutes on weekdays.
On 20 May 2026, electrive reported that MPT will add 40 electric buses, and that the government said the fleet will "eventually more than double in size." The same article recalls that 30 electric buses and a charging depot were added in 2023.
These figures come from the ministry and the press, not from MPT's tracking data, so they say nothing about the quality of the feed. What they show is the pressure on the data. Every frequency change alters the planned position that arrival estimates are compared with. Every new vehicle has to be paired with the right service from the first day. A network that adds buses and changes timetables twice in a few weeks needs its planned data and its live data to be updated together.
What should an AVM guarantee when many channels share one feed?
The Malta example points to five requirements that any operator can put in a specification.
- A single published feed. App, QR code, SMS and stop screens read the same arrival data, so they cannot disagree.
- A visible freshness rule. MPT greys out a bus after 1 minute without a position. A rule like this protects passengers from stale estimates, and it should be defined in the system rather than left to each screen.
- Planned data that changes with the timetable. When a frequency changes, the planned positions used for estimates change on the same date.
- Diversions recorded once. A diversion decided in the control room reaches every channel and the driver from one entry.
- Alerts that reach control quickly. Service breaks and critical delays should surface to the controller, not wait for a passenger complaint.
Pysae's platform page lists capabilities that map to this list. Under Operations, it lists a live map with delays, advances and regularity per line, alerts and incidents with immediate escalation for service breaks and critical delays, and Pysae Driver with a digital duty sheet, GPS guidance and two-way communication with the control room. It also lists automatic GTFS-RT, SIRI and ITxPT exports under Operations. Under Network, it lists calendars and exceptions, and a certified GTFS and NeTEx export to regional journey planners. The platform page also lists passenger information among the features. How a given network wires these together depends on its vehicles, its screens and its existing systems.
How can an operator test its own real-time quality?
An operator does not need a new tool to start. Four checks can be run with the data already available.
- Compare channels. Pick ten stops and compare the arrival estimate in the app, on the screen and by SMS at the same minute. Any difference points to a feed that is not shared.
- Measure position age. For each vehicle, record the time between positions. MPT states a transmission interval of about 5 seconds, so a network can set its own target and see how often it is missed.
- Stage a diversion. Record a planned diversion in the data and watch how every channel behaves before, during and after it.
- Review the grey-outs. Count how many vehicles lose their position for a minute or more and where, because poor coverage is one cause MPT itself names.
None of these checks needs a published benchmark. They compare the system with itself, which is the fair way to start.
What does this mean for operators outside Malta?
Malta publishes a clear description of how its tracking works, which makes it a good case to study. The same questions apply to a regional operator in Ireland or a city network in Canada: how fresh is the position, which planned data is it compared with, and how fast does a diversion reach the passenger. The answers are specific to each network, and Pysae is priced per vehicle and adapted to each network.
To see how Operations, Network and the passenger information features work together on your own network, use the Request a demo button on this page and tell us about your vehicles, your screens and your current feed.
Frequently asked questions
How often do Malta's buses send their position?
According to Malta Public Transport's tracking page, the bus transmits its location approximately every 5 seconds via GPS. If the app does not receive the latest GPS location within 1 minute, the bus icon greys out.
Where can passengers see real-time bus information in Malta?
MPT's page names the tallinja app, a QR code on the bus stop timesheet and an SMS to 5061 1010 with the bus stop code. A May 2026 announcement adds digital signage in six locations, including Valletta Terminal and Malta International Airport.
What limits the accuracy of real-time tracking?
MPT says that poor cellular network coverage may affect the update frequency and that bus visibility may be affected if a route is diverted or altered unexpectedly. Its page also says offline use is not supported.
Does an arrival estimate come from GPS alone?
No. MPT's 2016 announcement describes a comparison between each bus's current location and its planned position, and its tracking page says the estimate considers the bus's speed and other parameters. Planned data and live data both matter.
What should an operator specify for real-time passenger information?
A single published feed for all channels, a freshness rule, planned data that follows each timetable change, diversions recorded once, and alerts that reach control. These points come from the operator practices described above, not from a standard.