APRS Packet Errors for SR2XHG (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)	Packet
20260208131527	SP2EGA-2>APDW17,WIDE2-1,qAR,SR2NWG:)SR2XHG!5420.98N1842.26E-PHG1410 10368.88 MHz beacon
20260208134526	SP2EGA-2>APDW17,WIDE2-1,qAR,SR2NWG:)SR2XHG!5420.98N1842.26E-PHG1410 10368.88 MHz beacon
20260208144526	SP2EGA-2>APDW17,WIDE2-1,qAR,SR2NWG:)SR2XHG!5420.98N1842.26E-PHG1410 10368.88 MHz beacon
20260208151526	SP2EGA-2>APDW17,WIDE2-1,qAR,SR2NWG:)SR2XHG!5420.98N1842.26E-PHG1410 10368.88 MHz beacon
20260208154526	SP2EGA-2>APDW17,WIDE2-1,qAR,SR2NWG:)SR2XHG!5420.98N1842.26E-PHG1410 10368.88 MHz beacon
20260208161526	SP2EGA-2>APDW17,WIDE2-1,qAR,SR2NWG:)SR2XHG!5420.98N1842.26E-PHG1410 10368.88 MHz beacon
20260208164525	SP2EGA-2>APDW17,WIDE2-1,qAR,SR2NWG:)SR2XHG!5420.98N1842.26E-PHG1410 10368.88 MHz beacon
20260208171525	SP2EGA-2>APDW17,WIDE2-1,qAR,SR2NWG:)SR2XHG!5420.98N1842.26E-PHG1410 10368.88 MHz beacon
20260208174526	SP2EGA-2>APDW17,WIDE2-1,qAR,SR2NWG:)SR2XHG!5420.98N1842.26E-PHG1410 10368.88 MHz beacon
20260208181526	SP2EGA-2>APDW17,WIDE2-1,qAR,SR2NWG:)SR2XHG!5420.98N1842.26E-PHG1410 10368.88 MHz beacon
20260208184526	SP2EGA-2>APDW17,WIDE2-1,qAR,SR2NWG:)SR2XHG!5420.98N1842.26E-PHG1410 10368.88 MHz beacon