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
20190418114523SR2W>BEACON,TCPIP*,qAC,T2POLAND:@181145z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190418123024SR2W>BEACON,TCPIP*,qAC,T2POLAND:@181230z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190418124546SR2W>BEACON,TCPIP*,qAC,T2POLAND:@181245z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190418133028SR2W>BEACON,TCPIP*,qAC,T2POLAND:@181330z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190418134550SR2W>BEACON,TCPIP*,qAC,T2POLAND:@181345z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190418140029SR2W>BEACON,TCPIP*,qAC,T2POLAND:@181400z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190418143031SR2W>BEACON,TCPIP*,qAC,T2POLAND:@181430z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190418151534SR2W>BEACON,TCPIP*,qAC,T2POLAND:@181515z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190418154536SR2W>BEACON,TCPIP*,qAC,T2POLAND:@181545z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190418164540SR2W>BEACON,TCPIP*,qAC,T2POLAND:@181645z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190418170042SR2W>BEACON,TCPIP*,qAC,T2POLAND:@181700z5238.17N/#01902.63E-WX3IN1 Wloclawek digi