APRS Packet Errors for SA6BJE-4 (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
20260208132427SA6BJE-4>APOT30,WIDE2-2,qAR,SK6BA-1:!5722.75N/01227.04E_.../...g...t049T2WX
20260208135428SA6BJE-4>APOT30,WIDE2-2,qAR,SK6BA-1:!5722.75N/01227.04E_.../...g...t049T2WX
20260208142428SA6BJE-4>APOT30,WIDE2-2,qAR,SK6BA-1:!5722.75N/01227.04E_.../...g...t049T2WX
20260208145429SA6BJE-4>APOT30,WIDE2-2,qAR,SK6BA-1:!5722.75N/01227.04E_.../...g...t047T2WX
20260208152429SA6BJE-4>APOT30,WIDE2-2,qAR,SK6BA-1:!5722.75N/01227.04E_.../...g...t046T2WX
20260208155430SA6BJE-4>APOT30,WIDE2-2,qAR,SK6BA-1:!5722.75N/01227.04E_.../...g...t045T2WX
20260208162430SA6BJE-4>APOT30,WIDE2-2,qAR,SK6BA-1:!5722.75N/01227.04E_.../...g...t044T2WX
20260208165431SA6BJE-4>APOT30,WIDE2-2,qAR,SK6BA-1:!5722.75N/01227.04E_.../...g...t043T2WX
20260208172432SA6BJE-4>APOT30,WIDE2-2,qAR,SK6BA-1:!5722.75N/01227.04E_.../...g...t043T2WX
20260208175432SA6BJE-4>APOT30,WIDE2-2,qAR,SK6BA-1:!5722.75N/01227.04E_.../...g...t042T2WX
20260208182433SA6BJE-4>APOT30,WIDE2-2,qAR,SK6BA-1:!5722.75N/01227.04E_.../...g...t041T2WX