APRS Packet Errors for FW0562 (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
20260208150635FW0562>APN000,TCPXX*,qAX,CWOP-5:@081506z5049.17N/00432.88E_092/000g005t057r000p000P000b10064h65eMB63
20260208163635FW0562>APN000,TCPXX*,qAX,CWOP-4:@081636z5049.17N/00432.88E_103/000g000t052r000p000P000b10062h74eMB63
20260208170645FW0562>APN000,TCPXX*,qAX,CWOP-5:@081706z5049.17N/00432.88E_065/000g000t050r000p000P000b10067h79eMB63
20260208173643FW0562>APN000,TCPXX*,qAX,CWOP-4:@081736z5049.17N/00432.88E_088/000g004t048r000p000P000b10067h81eMB63
20260208180637FW0562>APN000,TCPXX*,qAX,CWOP-6:@081806z5049.17N/00432.88E_109/000g005t047r000p000P000b10070h84eMB63
20260208183639FW0562>APN000,TCPXX*,qAX,CWOP-5:@081836z5049.17N/00432.88E_098/000g005t045r000p000P000b10071h87eMB63
20260208193719FW0562>APN000,TCPXX*,qAX,CWOP-4:@081937z5049.17N/00432.88E_098/000g000t042r000p000P000b10071h89eMB63
20260208200715FW0562>APN000,TCPXX*,qAX,CWOP-4:@082007z5049.17N/00432.88E_098/000g000t041r000p000P000b10072h91eMB63
20260208203730FW0562>APN000,TCPXX*,qAX,CWOP-4:@082037z5049.17N/00432.88E_098/000g000t039r000p000P000b10071h92eMB63