APRS Packet Errors for KD4APP (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
20260208131948KD4APP>APN000,TCPIP*,qAC,T2CAEAST:@081319z3451.47N/08356.16W_180/000g000t025r000p000P000b09462h62L021eMB57
20260208151952KD4APP>APN000,TCPIP*,qAC,T2UKRAINE:@081519z3451.47N/08356.16W_234/000g000t035r000p000P000b09472h44L062eMB57
20260208161953KD4APP>APN000,TCPIP*,qAC,T2TURKIYE:@081619z3451.47N/08356.16W_197/000g000t043r000p000P000b09469h30L041eMB57
20260208171958KD4APP>APN000,TCPIP*,qAC,T2ERFURT:@081719z3451.47N/08356.16W_181/000g000t048r000p000P000b09465h26L030eMB57
20260208182001KD4APP>APN000,TCPIP*,qAC,T2ERFURT:@081819z3451.47N/08356.16W_173/000g000t051r000p000P000b09459h26L040eMB57