APRS Packet Errors for SR2W (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
20190220074011SR2W>BEACON,TCPIP*,qAC,T2POLAND:@200740z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220075512SR2W>BEACON,TCPIP*,qAC,T2POLAND:@200755z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220081013SR2W>BEACON,TCPIP*,qAC,T2POLAND:@200810z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220082514SR2W>BEACON,TCPIP*,qAC,T2POLAND:@200825z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220084015SR2W>BEACON,TCPIP*,qAC,T2POLAND:@200840z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220085516SR2W>BEACON,TCPIP*,qAC,T2POLAND:@200855z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220091016SR2W>BEACON,TCPIP*,qAC,T2POLAND:@200910z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220092517SR2W>BEACON,TCPIP*,qAC,T2POLAND:@200925z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220094018SR2W>BEACON,TCPIP*,qAC,T2POLAND:@200940z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220095519SR2W>BEACON,TCPIP*,qAC,T2POLAND:@200955z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220101020SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201010z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220102521SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201025z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220104022SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201040z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220105522SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201055z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220111023SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201110z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220112524SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201125z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220114025SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201140z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220115526SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201155z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220121027SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201210z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220122529SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201225z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220124029SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201240z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220125530SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201255z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220131030SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201310z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190220132531SR2W>BEACON,TCPIP*,qAC,T2POLAND:@201325z5238.17N/#01902.63E-WX3IN1 Wloclawek digi