APRS Packet Errors for CT1ETE-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
20260208133335CT1ETE-13>APN000,TCPIP*,qAC,NINTH:@081332z4127.11N/00815.77W_209/006g014t053r000p039P007b10118h77eMB63
20260208143337CT1ETE-13>APN000,TCPIP*,qAC,FIRST:@081432z4127.11N/00815.77W_218/004g013t053r000p032P007b10109h79eMB63
20260208153337CT1ETE-13>APN000,TCPIP*,qAC,THIRD:@081532z4127.11N/00815.77W_211/004g009t052r000p030P007b10109h76eMB63
20260208161841CT1ETE-13>APN000,TCPIP*,qAC,SEVENTH:@081617z4127.11N/00815.77W_191/006g014t051r000p030P007b10105h77eMB63
20260208184935CT1ETE-13>APN000,TCPIP*,qAC,EIGHTH:@081848z4127.11N/00815.77W_.../...g...t048r006p027P013b10097h75eMB63