APRS Packet Errors for KD2IXC-13 (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
20260209092352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t-11h68
20260209095352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t-10h69
20260209102352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t-11h69
20260209105352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t-11h70
20260209112352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t-11h70
20260209115352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t-11h70
20260209122352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t-12h70
20260209125352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t-11h71
20260209132352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t-07h72
20260209135352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t-01h80
20260209142352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t003h74
20260209145352KD2IXC-13>APDW15,qAO,KD2IXC-13:!4245.54N/07338.92W_.../...g...t005h72