APRS Packet Errors for ON6ZQ (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
20260928222910ON6ZQ>N100,TCPIP*,HIRD,qAR,AE7AF:;JA/NN-0282229z3604.S13819.E;S. plannon 20261004 0z
20260928223739ON6ZQ>APN100,TCPI,qAS,AE7AF:;GS-108225735.29NS00531.37W; acted on 20269 1100z
20260928231224ON6ZQ>AP,TCPIPTH,qAR,AE7AF:;W7010*22442.23N1270WS plann 20261400z
20260928231301ON6ZQ>APN100,CPPC,SIXT,qAS,AE7AF:;782313z1.09NSTA activ. pned on26100300z
20260928232158ON6ZQ>APN0,TCPIqAC,EHTH,qAR,AE7AF:;W7A/CS03282z509NS53W;annd21003 1z
20260929015822ON6ZQ>APN0,TCPI*,qAS,AE7AF:;VE7/FV604*111111z4910.11221.73W ttpson6zq.bE7/604
20260929025421ON6ZQ>APN100,TCPIP*,qAS,AE7AF:;GW03*2254z525003lannd on 202610