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
20260914142241SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260914145742SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260914153244SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260914160746SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260914164248SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260914171750SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260914175252SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260914182754SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260914190255SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260914193757SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20260914201259SR1NRD>APMI01,TCPIP*,qAC,T2POLNW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow