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
20190419053127SR2W>BEACON,TCPIP*,qAC,T2POLAND:@190531z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190419063128SR2W>BEACON,TCPIP*,qAC,T2POLAND:@190631z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190419073132SR2W>BEACON,TCPIP*,qAC,T2POLAND:@190731z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190419073142SR2W>BEACON,WIDE1-1,qAR,SR2BRO:;4s8.025-g*181035z5239.97N/019$3.68ErT082 -7600kHz R25 SR2W
20190419083135SR2W>BEACON,TCPIP*,qAC,T2POLAND:@190831z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190419093138SR2W>BEACON,TCPIP*,qAC,T2POLAND:@190931z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190419103141SR2W>BEACON,TCPIP*,qAC,T2POLAND:@191031z5238.17N/#01902.63E-WX3IN1 Wloclawek digi
20190419110143SR2W>BEACON,TCPIP*,qAC,T2POLAND:@191101z5238.17N/#01902.63E-WX3IN1 Wloclawek digi