APRS Packet Errors for 9W2SGJ-1 (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
202602081436479W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081451489W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081506509W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081521509W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081536509W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081551519W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081606349W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081621349W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081636359W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081651369W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081706369W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081721389W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081736399W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081751399W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081806419W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081821429W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081836439W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081851439W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081906449W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1
202602081921459W2SGJ-1>APLRG1,TCPIP*,qAC,MYAPRS:!LM&oTh1