APRS Packet Errors for KI5QPX-10 (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
20260208140429KI5QPX-10>APDW14,CABALL*,WIDE2-2,qAO,N7SGT-10:!3222.54NS10648.16W#PHG2120 KI5QPX IGate,Las Cruces NM
20260208140450KI5QPX-10>APDW14,TCPIP*,qAC,T2CAEAST:!3222.54NT10648.16W& KI5QPX IGate
20260208150429KI5QPX-10>APDW14,CABALL*,WIDE2-2,qAO,N7SGT-10:!3222.54NS10648.16W#PHG2120 KI5QPX IGate,Las Cruces NM
20260208150439KI5QPX-10>APDW14,TCPIP*,qAC,T2CAEAST:!3222.54NT10648.16W& KI5QPX IGate
20260208160429KI5QPX-10>APDW14,CABALL*,WIDE2-2,qAO,N7SGT-10:!3222.54NS10648.16W#PHG2120 KI5QPX IGate,Las Cruces NM
20260208160439KI5QPX-10>APDW14,TCPIP*,qAC,T2CAEAST:!3222.54NT10648.16W& KI5QPX IGate
20260208170429KI5QPX-10>APDW14,CABALL*,WIDE2-2,qAO,N7SGT-10:!3222.54NS10648.16W#PHG2120 KI5QPX IGate,Las Cruces NM
20260208170439KI5QPX-10>APDW14,TCPIP*,qAC,T2CAEAST:!3222.54NT10648.16W& KI5QPX IGate
20260208180429KI5QPX-10>APDW14,CABALL*,WIDE2-2,qAO,N7SGT-10:!3222.54NS10648.16W#PHG2120 KI5QPX IGate,Las Cruces NM
20260208180439KI5QPX-10>APDW14,TCPIP*,qAC,T2CAEAST:!3222.54NT10648.16W& KI5QPX IGate
20260208190429KI5QPX-10>APDW14,CABALL*,WIDE2-2,qAO,N7SGT-10:!3222.54NS10648.16W#PHG2120 KI5QPX IGate,Las Cruces NM
20260208190439KI5QPX-10>APDW14,TCPIP*,qAC,T2CAEAST:!3222.54NT10648.16W& KI5QPX IGate