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
20261020205404SR1NRD>APMI01,TCPIP*,qAC,T2HUN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020205705SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020212306SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020212906SR1NRD>APMI01,TCPIP*,qAC,T2HUN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020214908SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020220408SR1NRD>APMI01,TCPIP*,qAC,T2HUN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020221509SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020223909SR1NRD>APMI01,TCPIP*,qAC,T2HUN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020224111SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020230712SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020231411SR1NRD>APMI01,TCPIP*,qAC,T2HUN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020233313SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020234913SR1NRD>APMI01,TCPIP*,qAC,T2HUN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261020235915SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261021002415SR1NRD>APMI01,TCPIP*,qAC,T2HUN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261021002516SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261021005118SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261021005917SR1NRD>APMI01,TCPIP*,qAC,T2HUN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261021011719SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261021013419SR1NRD>APMI01,TCPIP*,qAC,T2HUN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261021014320SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261021020921SR1NRD>APMI01,TCPIP*,qAC,T2HUN:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow
20261021023523SR1NRD>APMI01,WIDE2-2,qAR,SR1WXW:;EPSC*111111z5335.10N/01454.06E^EPSC Szczecin - Goleniow