APRS Packet Errors for SR1NRD (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
20250916190118SR1NRD>APMI01,TCPIP*,qAC,T2DENMARK:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916190819SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916193421SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916193620SR1NRD>APMI01,TCPIP*,qAC,T2DENMARK:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916200022SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916201122SR1NRD>APMI01,TCPIP*,qAC,T2DENMARK:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916202624SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916204624SR1NRD>APMI01,TCPIP*,qAC,T2DENMARK:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916205225SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916211826SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916212126SR1NRD>APMI01,TCPIP*,qAC,T2DENMARK:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916214429SR1NRD>APMI01,SR1RES*,WIDE2-1,qAR,SR1SZD:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916215627SR1NRD>APMI01,TCPIP*,qAC,T2DENMARK:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916221029SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916223129SR1NRD>APMI01,TCPIP*,qAC,T2DENMARK:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916223630SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916230232SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916230631SR1NRD>APMI01,TCPIP*,qAC,T2SPAIN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916232833SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916234133SR1NRD>APMI01,TCPIP*,qAC,T2SPAIN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250916235435SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow