APRS Packet Errors for G8XXM-2 (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
20260208163501G8XXM-2>APN100,TCPIP*,qAC,CWOP-6:=5200.55N/00047.22W_000/000g...t...b10035
20260208170004G8XXM-2>APN100,TCPIP*,qAC,CWOP-4:=5200.55N/00047.22W_000/000g...t...b10035
20260208173503G8XXM-2>APN100,TCPIP*,qAC,CWOP-4:=5200.55N/00047.22W_000/000g...t...b10035
20260208180001G8XXM-2>APN100,TCPIP*,qAC,CWOP-7:=5200.55N/00047.22W_000/000g...t...b10035
20260208183502G8XXM-2>APN100,TCPIP*,qAC,CWOP-7:=5200.55N/00047.22W_000/000g...t...b10039
20260208190001G8XXM-2>APN100,TCPIP*,qAC,CWOP-5:=5200.55N/00047.22W_000/000g...t...b10038
20260208193501G8XXM-2>APN100,TCPIP*,qAC,CWOP-3:=5200.55N/00047.22W_000/000g...t...b10038
20260208200001G8XXM-2>APN100,TCPIP*,qAC,CWOP-3:=5200.55N/00047.22W_000/000g...t...b10039
20260208203502G8XXM-2>APN100,TCPIP*,qAC,CWOP-6:=5200.55N/00047.22W_000/000g...t...b10037
20260208210001G8XXM-2>APN100,TCPIP*,qAC,CWOP-3:=5200.55N/00047.22W_000/000g...t...b10036
20260208213501G8XXM-2>APN100,TCPIP*,qAC,CWOP-3:=5200.55N/00047.22W_000/000g...t...b10037
20260208220004G8XXM-2>APN100,TCPIP*,qAC,CWOP-7:=5200.55N/00047.22W_000/000g...t...b10036