WA Radio Scanner Users' Group

synx wrote: Fri Nov 28, 2025 11:47 am And not even the digital we can listen to
Why couldn't they just merge with the bus cap + dmr

Because of the Communications Based Train Control (CBTC) that will be rolled out in the future. It all works in with that as far as I'm aware.

Hi! Transperth buses are typically coordinated through a central radio dispatch control room to ensure efficient communication and management across the network. The talkgroup IDs you've noticed are likely part of this centralized system, allowing drivers to communicate directly with dispatch for ...

Network Control frequencies or Rail Security?

No, there is no central control room as Transperth is only the brand banner that the buses operate under...

From memory 801xx is PATH Transit
802xx is Swan Transit
800xx is Transdev. The last digit is what defines who's talkgroup it is (or what "Channel").

CCR is the callsign for the PATH Transit ...

Shift Numbers now have to be called as "November Three One", "Charlie Seven","Sierra Two One" as apposed to "C20", "N4", S18" etc...

Metro Control is also now known as Network Control.

"Driver No's" are the service number, which changes each trip

Well I "figured" it out from when a Mandurah unit had an open channel and base alerted to which WT is was, put 2 and 2 together and I assume that they're handhelds. The selcall correlates to their staff number, if you look on their name badge it has a 5 digit number, same as the 5 digit CCIR tone ...

Interesting to see that Butler ended up with the old Perth 2nd!

Great shots, thanks for sharing!

Hi all,

Thought it would be worth firing up my updated list for Perth's Bus network.

Swan Transit# :

Southern River 474.7500
Beckenham, Canning Vale: 473.2500
Circle Route*: 472.7500
Karrinyup, Beenyup: 470.3750
Ellenbrook, Midvale, Mundaring: 470.6750
Ellenbrook, Midvale, Mundaring**: 472.9750 ...

Special Events Channel (473.075) for the Busport Control Room

5-Tone. CCIR1

Main Power Distribution Board decided it wanted to go on strike, and therefore did so with a rather large bang.

One of my sources has informed me, that the problem has been found and rectified. I'm not going to say anymore just yet... We'll wait and see if there are any more problems in the near future first.

If this is the one I think it is, I've heard from various sources that this one was an electrical fire & had nothing to do with the previous fires. Apparently the engine was undamaged

Driver would have had prior permission from "Mobile 4" (circle route manager) to run 000 to another point on the circle route to make up time due to late running

That's rather interesting, as I find the OC's have a lot more room than the B7RLE's, but then again, that could just be my imagination