APRS Packet Errors for IZ4ISC-20 (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
20260209091046IZ4ISC-20>APRSMC,TCPIP*,qAR,T79A-10:!4446.10N/01208.59E&MC Lagosanto#iz4isc-20/B=100/A=000138
20260209094101IZ4ISC-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4446.10N/01208.59E&MC Lagosanto#iz4isc-20/B=100/A=000138
20260209101119IZ4ISC-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4446.10N/01208.59E&MC Lagosanto#iz4isc-20/B=100/A=000138
20260209104134IZ4ISC-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4446.10N/01208.59E&MC Lagosanto#iz4isc-20/B=100/A=000138
20260209111145IZ4ISC-20>APRSMC,TCPIP*,qAR,T79A-10:!4446.10N/01208.59E&MC Lagosanto#iz4isc-20/B=100/A=000138
20260209114201IZ4ISC-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4446.10N/01208.59E&MC Lagosanto#iz4isc-20/B=100/A=000138
20260209121216IZ4ISC-20>APRSMC,TCPIP*,qAR,T79A-10:!4446.10N/01208.59E&MC Lagosanto#iz4isc-20/B=100/A=000138
20260209124239IZ4ISC-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4446.10N/01208.59E&MC Lagosanto#iz4isc-20/B=100/A=000138
20260209131248IZ4ISC-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4446.10N/01208.59E&MC Lagosanto#iz4isc-20/B=100/A=000138
20260209134305IZ4ISC-20>APRSMC,TCPIP*,qAR,T79A-10:!4446.10N/01208.59E&MC Lagosanto#iz4isc-20/B=100/A=000138
20260209141318IZ4ISC-20>APRSMC,TCPIP*,qAR,T79A-10:!4446.10N/01208.59E&MC Lagosanto#iz4isc-20/B=100/A=000138