APRS Packet Errors for 9W2UXP-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
202602091033539W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091049009W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091104079W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091119159W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091134229W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091149299W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091204369W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091219439W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091234509W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091249579W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091305049W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091320119W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091335189W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091350259W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091405329W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS
202602091420399W2UXP-10>APLRG1,TCPIP*,qAC,T2POLC:!LLxSqh4Cma GLoRa APRS