Passenger information in the context of delays
On May 6, 2026, A Voz da Serra published a story about congestion and bus delays in Nova Friburgo. The text recorded passenger complaints and the position of Faol, which pointed to traffic as one of the main causes of delays.
In that context, the article presented the Partiu App as an option to look up lines, nearby stops and arrival predictions. The address given was friburgo.merustracker.com.br/consultapassageiro.
Making the trip visible
For someone waiting at the stop, knowing the bus position and arrival prediction can help follow the trip. This information makes the situation easier to understand, but it does not remove congestion or, on its own, solve supply or regularity problems.
It is also useful to distinguish the information shown to the passenger from the analysis done by an operations team. The lookup answers questions about the trip; comparing schedule and execution serves a different management need. In the Merus product, this second perspective is described in planned versus actual.
What the story documents
The story confirms a new public mention of the lookup hosted on the Merus domain, months after the January coverage. It does not present a performance evaluation of the software, nor does it credit the platform with solving the reported delays.
The relevant takeaway for this blog is the tool's presence among the passenger information channels. Vehicle operation remains the carrier's responsibility. See how Merus presents its ability to web lookup and ETA.
In public transport, the same logic supports public transport oversight: trips, kilometres and subsidy.
