[FedCom] FedCom Digest, Vol 147, Issue 2
Wilrobnson
wilrobnson at gmail.com
Mon Nov 7 08:55:09 EST 2022
Too many RIDs. USCG Sector Seattle has 2 armed gate guards and sometimes a
third roving around. I verified them a few years ago on 395.xxxx (I
forget) in simplex, encrypted. At that time they were carrying Harris
portables.
Based on my knowledge of fed stuff in Seattle, both as a scanner bunny and
a former Fed, I still lean 95% towards the VA. It's not their police nor
is it their engineering/facilities types, so I guess housekeeping type
stuff (Seattle VAPD just last year got a slew of new APX portables/mobiles,
and facilities types are on an IDAS system).
-Wil
>
> Subject: Re: [FedCom] Seattle Area Fed Mystery
> Message-ID:
> <
> CABvW5WBJEFCvEpU13n_Whpw5hw6ML6yCqGH1Hp-ziRGZy_MT+w at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Based on the frequency used and the location description I'd guess it's
> Coast Guard security.
>
> -Eric
>
> On Sun, Nov 6, 2022, 9:38 PM Nick Carrigan <cnick66qn0 at gmail.com> wrote:
>
> > Could use some help tracking down a mystery DMR site in the Seattle area.
> > It's a DMR repeater on 410.9 and the users are using BP encryption with
> > RAS. I'm pretty sure it's from the downtown Seattle area but it's not
> from
> > the VA Hospital.
> >
> > They were using the 8xxx RIDs below but it appears like they have moved
> to
> > 5xxx RIDs for some strange reason. They have NEVER dropped encryption so
> > it's a well-secured channel. The transmissions are brief and rarely go
> > beyond 10 secs. It smells of building security. Maintenance or other
> > services are pretty yakky. The activity is pretty light but they seem to
> > start around 5AM and generally stop by 6PM with very few radio checks
> > in-between those hours.
> >
> > Here's my monitoring data from it:
> >
> > (DMR, CC:13, SLOT 1)
> > BASIC PRIVACY! RAS!
> > -------------
> > UNIQUE RIDs:
> > ------------
> > 133
> > 136
> > 173
> > 256
> > 282 (NEW - 10/21/2022)
> > 306
> > 312
> > 403
> > 493
> > 529
> > 535
> > 582
> > 650 (NEW - 11/17/2021)
> > 672 (NEW - 12/5/2021)
> > 673
> > 683
> > 713
> > 778
> > 782
> > 804
> > 921
> > 1026
> > 5003 (NEW - 10/23/2022)
> > 5004 (NEW - 10/24/2022)
> > 5005 (NEW - 10/22/2022)
> > 5007 (NEW - 10/21/2022)
> > 5008 (NEW - 10/26/2022)
> > 5010 (NEW - 10/24/2022)
> > 5014 (NEW - 10/31/2022)
> > 5016 (NEW - 10/21/2022)
> > 5017 (NEW - 10/23/2022)
> > 5019 (NEW - 10/23/2022)
> > 5025 (NEW - 10/28/2022)
> > 8033
> > 8061
> > 8066
> > 8067 (NEW - 1/5/2021)
> > 8089
> > 8191
> > 8198
> > 8303
> > ______________________________________________________________
> > FedCom mailing list
> > Home: http://mailman.qth.net/mailman/listinfo/fedcom
> > Help: http://mailman.qth.net/mmfaq.htm
> > Post: mailto:FedCom at mailman.qth.net
> >
> > This list hosted by: http://www.qsl.net
> > Please help support this email list: http://www.qsl.net/donate.html
> >
>
>
> ------------------------------
>
> _______________________________________________
> FedCom mailing list
> FedCom at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/fedcom
>
>
> End of FedCom Digest, Vol 147, Issue 2
> **************************************
>
More information about the FedCom
mailing list