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
20260728080057SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260728083559SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260728091100SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260728094602SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260728102104SR1NRD>APMI01,TCPIP*,qAC,T2TAS:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260728105606SR1NRD>APMI01,TCPIP*,qAC,T2CAEAST:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260728113108SR1NRD>APMI01,TCPIP*,qAC,T2CAEAST:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260728120610SR1NRD>APMI01,TCPIP*,qAC,T2CAEAST:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260728124112SR1NRD>APMI01,TCPIP*,qAC,T2TAS:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260728131613SR1NRD>APMI01,TCPIP*,qAC,T2PRT:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260728135115SR1NRD>APMI01,TCPIP*,qAC,T2BELGIUM:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow