Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LF\:\s+WG2XWS\s+false\s+decode\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LF\:\s+WG2XWS\s+false\s+decode\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: LF: WG2XWS false decode (score: 1): Author: "Michael Sapp" <[email protected]>; Date: Mon, 07 Mar 2016 09:14:10 -0500; Hi All: The WG2XWS call is in the FCC data base as issued to Northrop Grumman and based in Georgetown NJ. It appears to be a false decode even though more than one station reported it in the WSPR dat; /rsgb_lf_group-archives/html/rsgb_lf_group/2016-03/msg00098.html (18,768 bytes)
2. Re: LF: WG2XWS false decode (score: 1): Author: "Alan Melia" <[email protected]>; Date: Mon, 07 Mar 2016 15:45:13 +0100; Thanks Michael, That confirms my caution about accepting spots at face value. I suspect once a False Decode has been registered/uploaded it becomes available as an actiive station in the list for oth; /rsgb_lf_group-archives/html/rsgb_lf_group/2016-03/msg00100.html (20,070 bytes)

Current List: 1 - 2
Page: [1]