APRS Packet Errors for IZ8FPF-21 (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
20260209094436IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394
20260209101448IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394
20260209104503IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394
20260209111518IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394
20260209114533IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394
20260209121551IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394
20260209124606IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394
20260209131621IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394
20260209134636IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394
20260209141651IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394
20260209144706IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394
20260209151721IZ8FPF-21>APRSGW,TCPIP*,qAR,IZ8FPF-21:!4110.99N/01405.90E&#iGate Meshcom/A=000394