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
20250912061631SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250912062531SR1NRD>APMI01,TCPIP*,qAC,T2SWEDEN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250912064236SR1NRD>APMI01,SR1BIA,SR1NDH,WIDE2*,qAR,SR2SLA:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250912070834SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250912081037SR1NRD>APMI01,TCPIP*,qAC,T2SWEDEN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250912101044SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250912110247SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250912110546SR1NRD>APMI01,TCPIP*,qAC,T2SWEDEN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250912112848SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250912114048SR1NRD>APMI01,TCPIP*,qAC,T2SWEDEN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20250912115449SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow