ok I am picking up 172.11250 here in the dc metro area and it is coming up under the Justice Integrated Wireless Network. So somehow 4F0 and 715 BEE0A are tired in to each other.
ok I am picking up 172.11250 here in the dc metro area and it is coming up under the Justice Integrated Wireless Network. So somehow 4F0 and 715 BEE0A are tired in to each other.
Coincidence. Different systems can use the same frequencies, doesn't mean they are related or linked in any way.ok I am picking up 172.11250 here in the dc metro area and it is coming up under the Justice Integrated Wireless Network. So somehow 4F0 and 715 BEE0A are tired in to each other.
SecondSince we have a lot of unconfirmed now, maybe it is time to start a wiki page so we have something to reference to.
Based on 2 days of driving around south and north, I think the 170.3375 site will be found in South NJ.
Strong reception into Wilmington but don't think TX is local. It fades deep as you head north from DE into PA/ west of Philly, and south via I-95 in to Maryland.
I get Site 110 (171.68750) strong in Eastern Monmouth County. Popped it into Pro96Com and discovered a bunch of new adjacent sites populated since last weekend when I last checked it out.
Site 101 (CC 406.61250) NYC
Site 1114 (CC 168.91250)
Site 1115 (CC 170.60000)
Site 1118 (CC 173.55000)
Site 1128 (CC 173.55000)
Site 1132 (CC 170.67500)
Besides 110, the only other CC I can only pickup is 173.55000 with only 1 bar and cannot decode.
Let's just clarify for those unfamiliar with how Pro96Com formats sites (combines RFSS+SiteID), that those are the following sites:Site 101 (CC 406.61250) NYC
Site 1114 (CC 168.91250)
Site 1115 (CC 170.60000)
Site 1118 (CC 173.55000)
Site 1128 (CC 173.55000)
Site 1132 (CC 170.67500)