APRS Packet Errors for KF0AIT-4 (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
20260208150151	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683
20260208153206	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683
20260208160221	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683
20260208163236	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683
20260208170251	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683
20260208173307	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683
20260208180322	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683
20260208183337	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683
20260208190352	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683
20260208193407	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683
20260208200422	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683
20260208203437	KF0AIT-4>APRSGW,TCPIP*,qAR,KF0AIT-4:!4418.04N/09646.20W>Meshcom Lora Node/B=100/A=001683