LMRN Technical Data Discussion

gary123

Member
Joined
Sep 11, 2002
Messages
2,991
Reaction score
1,417
If the KID is E01 then those will be new EMS TG. I have the RID in the middle of a pile of EMS RIDS. Also I think that is site 82
 

IdleMonitor

Member
Premium Subscriber
Joined
Feb 17, 2005
Messages
3,362
Reaction score
495
Location
The Ottawa Valley - Eastern Ontario
If the KID is E01 then those will be new EMS TG. I have the RID in the middle of a pile of EMS RIDS. Also I think that is site 82
These are the 2 that have been getting. They are 2 different sites. The talkgroups noted were from Site 82. Site 93 is also close to me. In fact I believe it's closer to me than Site 82. I'm in Renfrew. I don't have an SDR at the moment setup to track this stuff like you guys. I just noted what I saw come across ProScan today on the SDS 200. Site 82 NAC is AD2, Site 93 is AD0. KID =? what is KID?

AD91 (1)093 (5D)Site 93UNKNOWN142.470c
AD91 (1)082 (52)Mount St. PatrickRenfrew141.555c142.290
 

gary123

Member
Joined
Sep 11, 2002
Messages
2,991
Reaction score
1,417
KID is the encryption key used by the people on the channel. On encrypted systems like LMRN the KID can be used to rapidly identify the user on a unknown TG. All EMS TG use KID of 0E01 or KID 0022(patched). OPP detachments are almost all 0022 with the occasional 0301. The fun starts with the rest of the TG on LMRN they all seem to have different KIDs BUT many TG groupings (IE 800-010) use the same KID. This tells us that whoever it is they are all the same department or user.

Many of us are using DSD fastlane to capture this additional information. I do not know if other SDR programs are capable or not. Another thing DSD also decodes the over the air (OTA) user alias. In the case of EMS it identifies the exact EMS unit (IE 1061). So if you know the current EMS units in your area when they migrate to LMRN you will at least know if a local unit is on the air.
 

kybervon

Member
Joined
Dec 19, 2002
Messages
19
Reaction score
25
Location
Trenton, ON
I’m starting to see some encrypted activity again on Demorestville Tower. My Whistler shows the talk group as 693, which is odd to me. My Uniden HP2 shows it as 22103 which is ORNG LAND CC. There were a few hits yesterday and today. The LCN monitor still only showed the ‘two’ channels, which I assume to be the one, lonely frequency still.
 

mciupa

Canadian DB Admin
Moderator
Joined
Nov 5, 2002
Messages
8,937
Reaction score
2,446
Location
I'm here a lot
New capture from Site 9 Mississauga:


P25, BEE00.AD9, 11010, 502810, 50, Normal, 2, 2025/10/21 16:41, "", "MOE-M-502810", 89964538
 

kybervon

Member
Joined
Dec 19, 2002
Messages
19
Reaction score
25
Location
Trenton, ON
Once again, things were steady on Demorestville site today. One active TG was 20530 which is CISO Toronto. There was another busy TG which was 19264. I don't see it logged on the page as of yet. I understand from local media that OPP was busy again doing their "large investigation" on the Tynedinaga Mohawk Territory. It's been going on, sporadically, over the last couple of weeks. That all being said, and the range of the unidentified talkgroup, one might guess that this is another OPP specialty unit TG.

I've been running my HP-2 in analyze mode, logging the activity. Much of the log is written in language far above my pay-grade. If anyone feels they have the skillset and desire to interpret the results, I would be glad to share.
 

gary123

Member
Joined
Sep 11, 2002
Messages
2,991
Reaction score
1,417
always happy to look at logs. This is often where new information is discovered.
 

gary123

Member
Joined
Sep 11, 2002
Messages
2,991
Reaction score
1,417
It falls into the MOE RIDSs I have. The TG also is in the MOE TG range of 11xxx. I have a KID of 701 but this is unconfirmed..
 

kybervon

Member
Joined
Dec 19, 2002
Messages
19
Reaction score
25
Location
Trenton, ON
always happy to look at logs. This is often where new information is discovered.
The files are around 250 mb per. It seems to be just the same thing over and over, for the most part. Here is a snippet of what I'm seeing:

10/22/2025 10:14:48 "39,3900015603720403720451F0" Secondary Control Channel Broadcast
10/22/2025 10:14:48 "0B,0B9000000000000003649146" Reserved
10/22/2025 10:14:48 "3A,BA00003AD901560364606EEF" RFSS Status Broadcast Sid:AD9h Sub:1 Site:86 Lcn:868
10/22/2025 10:14:48 "3B,3B0000BEE00AD90364600DE6" Network Status Broadcast Wacn:BEE00h Sid:AD9h Lcn:868
10/22/2025 10:14:48 "05,059040008000000008007A9A" Unit To Unit Answer Request Tad:8388608 Src:2048
10/22/2025 10:14:48 "3C,BC00003AD9015503A0704E2D" Adjacent Status Broadcast
10/22/2025 10:14:48 "34,34000508603C019F0DE8D459" Identifier Update for VHF/UHF Bands Iden:0 Bw:5 Tofs:536 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "33,33001308603C019F0DE875DC" Identifier Update for TDMA Iden:1 Type:3 Tofs:536 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "34,B4002508703C019F0DE85181" Identifier Update for VHF/UHF Bands Iden:2 Bw:5 Tofs:540 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "30,300000046A33567152B6BADE" Reserved
10/22/2025 10:14:48 "33,33003308703C019F0DE81430" Identifier Update for TDMA Iden:3 Type:3 Tofs:540 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "34,B4004504A83C019F0DE827A4" Identifier Update for VHF/UHF Bands Iden:4 Bw:5 Tofs:298 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "33,33005304A83C019F0DE86215" Identifier Update for TDMA Iden:5 Type:3 Tofs:298 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "09,09901180000000000000E723" Reserved
10/22/2025 10:14:48 "39,B9000156037204037204B5C4" Secondary Control Channel Broadcast
10/22/2025 10:14:48 "3A,3A00003AD901560364608ADB" RFSS Status Broadcast Sid:AD9h Sub:1 Site:86 Lcn:868
10/22/2025 10:14:48 "3B,3B0000BEE00AD90364600DE6" Network Status Broadcast Wacn:BEE00h Sid:AD9h Lcn:868
10/22/2025 10:14:48 "05,859040008000000008009EAE" Unit To Unit Answer Request Tad:8388608 Src:2048
10/22/2025 10:14:48 "3C,3C00003AD90150032C7048A9" Adjacent Status Broadcast
10/22/2025 10:14:48 "34,34006504783C019F0DE81C4C" Identifier Update for VHF/UHF Bands Iden:6 Bw:5 Tofs:286 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "33,B3007304783C019F0DE859FD" Identifier Update for TDMA Iden:7 Type:3 Tofs:286 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "3D,3D00C325E032092ACD4057C3" Identifier Update for non-VHF/UHF Bands Iden:12 Bw:100 Tofs:376 Csp:50 Bfrq:153800000
10/22/2025 10:14:48 "30,300000046A33567152DE5770" Reserved
10/22/2025 10:14:48 "33,B300D3CB0032092ACD4016E4" Identifier Update for TDMA Iden:13 Type:3 Tofs:12992 Csp:50 Bfrq:153800000
10/22/2025 10:14:48 "3D,3D00E322D0320A253C940687" Identifier Update for non-VHF/UHF Bands Iden:14 Bw:100 Tofs:180 Csp:50 Bfrq:170212500
10/22/2025 10:14:48 "0B,0B9000000000000003649146" Reserved
10/22/2025 10:14:48 "33,B300F37080320A253C941C13" Identifier Update for TDMA Iden:15 Type:3 Tofs:7200 Csp:50 Bfrq:170212500
10/22/2025 10:14:48 "09,09901180000000000000E723" Reserved
10/22/2025 10:14:48 "39,3900015603720403720451F0" Secondary Control Channel Broadcast
10/22/2025 10:14:48 "3A,BA00003AD901560364606EEF" RFSS Status Broadcast Sid:AD9h Sub:1 Site:86 Lcn:868
10/22/2025 10:14:48 "3B,3B0000BEE00AD90364600DE6" Network Status Broadcast Wacn:BEE00h Sid:AD9h Lcn:868
10/22/2025 10:14:48 "05,059040008000000008007A9A" Unit To Unit Answer Request Tad:8388608 Src:2048
10/22/2025 10:14:48 "3C,BC00003AD901530370707C93" Adjacent Status Broadcast
10/22/2025 10:14:48 "34,34000508603C019F0DE8D459" Identifier Update for VHF/UHF Bands Iden:0 Bw:5 Tofs:536 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "33,33001308603C019F0DE875DC" Identifier Update for TDMA Iden:1 Type:3 Tofs:536 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "34,B4002508703C019F0DE85181" Identifier Update for VHF/UHF Bands Iden:2 Bw:5 Tofs:540 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "30,300000046A33567153105CC3" Reserved
10/22/2025 10:14:48 "33,33003308703C019F0DE81430" Identifier Update for TDMA Iden:3 Type:3 Tofs:540 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "34,B4004504A83C019F0DE827A4" Identifier Update for VHF/UHF Bands Iden:4 Bw:5 Tofs:298 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "33,33005304A83C019F0DE86215" Identifier Update for TDMA Iden:5 Type:3 Tofs:298 Csp:60 Bfrq:27201000
 

mciupa

Canadian DB Admin
Moderator
Joined
Nov 5, 2002
Messages
8,937
Reaction score
2,446
Location
I'm here a lot
What stands out to me is this line: 10/22/2025 10:14:48 "05,059040008000000008007A9A" Unit To Unit Answer Request Tad:8388608 Src:2048

I am wondering if that is the MTO Maintenance Eastern Patrol Control Centre. We have a block of talkgroups not recorded from 2028 to 2049.
Keep listening in the future as winter approaches and you may at some point hear Patrols 51 to 84 check in when they go live.
 

gary123

Member
Joined
Sep 11, 2002
Messages
2,991
Reaction score
1,417
I agree with mciupa on the 2048 TG, It sits right in the middle of the known MTO TG. Since this is a zone 2 site I think we will see more MTO show up in the next few months. The 8388608 does not match any RID. Its too long to be a different RID grouping.

The sections that contain the identifier update is the bandsplit data
10/22/2025 10:14:48 "34,34000508603C019F0DE8D459" Identifier Update for VHF/UHF Bands Iden:0 Bw:5 Tofs:536 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "33,33001308603C019F0DE875DC" Identifier Update for TDMA Iden:1 Type:3 Tofs:536 Csp:60 Bfrq:27201000
10/22/2025 10:14:48 "34,B4002508703C019F0DE85181" Identifier Update for VHF/UHF Bands Iden:2 Bw:5 Tofs:540 Csp:60 Bfrq:27201000

site info
RFSS Status Broadcast Sid:AD9h Sub:1 Site:86 Lcn:868
 

kybervon

Member
Joined
Dec 19, 2002
Messages
19
Reaction score
25
Location
Trenton, ON
I appreciate the help in interpreting the results. I will set up 2048 to record on my Whistler as it runs 24/7. November 1st is around the corner so I’ll hopefully catch those riveting hourly road reports.

I’m also watching the LCN’s as channels will likely be added at some point.
 

gary123

Member
Joined
Sep 11, 2002
Messages
2,991
Reaction score
1,417
Thanks to a member here who took a trip up north. This is some confirmed northern Ont Zone 2 sites.

Site: 1.24 ; DYERS_BAY

Channel 0-896: 142.725 CC

Site: 1.30 NAC=AD0 ; PENETANG

Neighbor: BEE00.AD9-1.24 ; DYERS_BAY
Neighbor: BEE00.AD9-1.29 ; OWEN_SOUND
Neighbor: BEE00.AD9-1.34 ; THORNBURY(Kimberley)
Neighbor: BEE00.AD9-1.35 ; WIARTON
Neighbor: BEE00.AD9-1.41 ; EDGAR
Neighbor: BEE00.AD9-1.42 ; WASHAGO
Neighbor: BEE00.AD9-1.72
Neighbor: BEE00.AD9-1.73 ; BRACEBRIDGE
Neighbor: BEE00.AD9-1.84 ; PARRY_SOUND
Neighbor: BEE00.AD9-1.92
Neighbor: BEE00.AD9-1.147 ; 147_TEMP_SITE

Channel 1-1652: 142.2-1 VOICE
Channel 1-1653: 142.2-2 VOICE
Channel 0-846: 142.35 CC
Channel 0-856: 142.425 DATA
Channel 1-1812: 142.8-1 VOICE
Channel 1-1813: 142.8-2 VOICE
Channel 0-942: 143.07 SCC

Site: 1.35 ; WIARTON

Channel 0-880: 142.605 CC

Site: 1.41 NAC=AD1 ; EDGAR

Neighbor: BEE00.AD9-1.6 ; PRIMROSE(Dufferin)
Neighbor: BEE00.AD9-1.26 ; SUNDERLAND
Neighbor: BEE00.AD9-1.30 ; PENETANG
Neighbor: BEE00.AD9-1.34 ; THORNBURY(Kimberley)
Neighbor: BEE00.AD9-1.39 ; KING_CITY
Neighbor: BEE00.AD9-1.42 ; WASHAGO
Neighbor: BEE00.AD9-1.58 ; FENELON_FALLS
Neighbor: BEE00.AD9-1.73 ; BRACEBRIDGE
Neighbor: BEE00.AD9-1.92
Neighbor: BEE00.AD9-1.110
Neighbor: BEE00.AD9-1.147 ; 147_TEMP_SITE

Channel 0-800: 142.005 DATA
Channel 1-1672: 142.275-1 VOICE
Channel 1-1673: 142.275-2 VOICE
Channel 0-866: 142.5 CC SCC
Channel 1-1748: 142.56-1 VOICE
Channel 1-1816: 142.815-1 VOICE
Channel 1-1817: 142.815-2 VOICE
Channel 0-928: 142.965 CC
Channel 1-1889: 143.085-2 VOICE


Site: 1.42 NAC=AD2 ; WASHAGO

Neighbor: BEE00.AD9-1.26 ; SUNDERLAND
Neighbor: BEE00.AD9-1.30 ; PENETANG
Neighbor: BEE00.AD9-1.41 ; EDGAR
Neighbor: BEE00.AD9-1.58 ; FENELON_FALLS
Neighbor: BEE00.AD9-1.73 ; BRACEBRIDGE
Neighbor: BEE00.AD9-1.89 ; MINDEN
Neighbor: BEE00.AD9-1.92
Neighbor: BEE00.AD9-1.110
Neighbor: BEE00.AD9-1.147 ; 147_TEMP_SITE

Channel 0-890: 142.68 CC
Channel 0-912: 142.845 SCC

Site: 1.73 NAC=AD9 ; BRACEBRIDGE

Neighbor: BEE00.AD9-1.30 ; PENETANG
Neighbor: BEE00.AD9-1.41 ; EDGAR
Neighbor: BEE00.AD9-1.42 ; WASHAGO
Neighbor: BEE00.AD9-1.58 ; FENELON_FALLS
Neighbor: BEE00.AD9-1.59 ; HALIBURTON
Neighbor: BEE00.AD9-1.75 ; BURKS_FALLS
Neighbor: BEE00.AD9-1.78 ; HILLSIDE
Neighbor: BEE00.AD9-1.84 ; PARRY_SOUND
Neighbor: BEE00.AD9-1.89 ; MINDEN
Neighbor: BEE00.AD9-1.92
Neighbor: BEE00.AD9-1.147 ; 147_TEMP_SITE

Channel 0-858: 142.44 SCC
Channel 0-896: 142.725 CC

Site: 1.92 NAC=AD0

Neighbor: BEE00.AD9-1.30 ; PENETANG
Neighbor: BEE00.AD9-1.41 ; EDGAR
Neighbor: BEE00.AD9-1.42 ; WASHAGO
Neighbor: BEE00.AD9-1.73 ; BRACEBRIDGE
Neighbor: BEE00.AD9-1.75 ; BURKS_FALLS
Neighbor: BEE00.AD9-1.78 ; HILLSIDE
Neighbor: BEE00.AD9-1.84 ; PARRY_SOUND

Channel 0-822: 142.17 SCC
Channel 0-892: 142.695 CC
 

VA3ADP

Active Member
Premium Subscriber
Joined
Mar 27, 2015
Messages
1,041
Reaction score
301
Location
Mississauga, Ontario Canada
Had some interesting ones off of Toronto over the last 12 hours;'

P25, BEE00.AD9, 22200, 790234, 50, Normal, 7, 2025/10/23 16:49, ""
P25, BEE00.AD9, 22200, 790284, 50, Normal, 11, 2025/10/23 16:49, ""
P25, BEE00.AD9, 22200, 790288, 50, Normal, 11, 2025/10/23 16:54, ""

P25, BEE00.AD9, 22205, 790011, 50, Normal, 0, 2025/10/23 16:46, ""
P25, BEE00.AD9, 22205, 790285, 50, Normal, 12, 2025/10/23 15:33, ""
P25, BEE00.AD9, 22205, 790287, 50, Normal, 6, 2025/10/23 15:32, ""
P25, BEE00.AD9, 22205, 790289, 50, Normal, 1, 2025/10/23 11:34, ""
P25, BEE00.AD9, 22205, 790291, 50, Normal, 13, 2025/10/23 15:35, ""

P25, BEE00.AD9, 696, 100500, 50, Normal, 197, 2025/10/23 18:53, "", "BEL-CRK-OP102", 453041B6
P25, BEE00.AD9, 696, 754289, 50, Normal, 2, 2025/10/23 16:02, "", "AH-GEO-MKSV", 422D0F5A

I had 22251 a while back with a "PSC" Alias. Not sure what PSC means...

Was interesting to see what also looks like a Bell Tech console on 100500

Also MKSV appears to indicate Markham-Stoufville Hospital.
 

gary123

Member
Joined
Sep 11, 2002
Messages
2,991
Reaction score
1,417
I can confirm 754289 is MARKHAM-STOUFFVILLE HOSPITAL.

Nice catch on the possible Bell console. This RID is all by its self but is near other Bell RIDs.

I have no names for the 222xx TG range. The RID range of 7902xx is also unknown. Based on other RID configurations It looks like 790011 is a dispatch unit and the other 7902xx are mobiles. Interesting there is no talker alias (OTA) so again based on other TGs this will be a law enforcement user.
 

mmisk

Member
Joined
Jul 4, 2003
Messages
822
Reaction score
220
Location
Ottawa Canada
I am in Ottawa and just noticed my first LMRN site.

;LMRN AD9 Site 064 Winchester Stormont, Dundas, Glengarry 141.390c 142.320c

Conditions must be very good this morning.

LMRN AD9 Site 066 Pendleton Prescott, Russell, United 142.365c

;LMRN AD9 Site 082 Mount St. Patrick Renfrew 141.555c 142.290
 
Last edited:
Top