APRS Packet Errors for G0FGX (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
20190923150303G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923152154G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923153717G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923155238G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923160800G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923162326G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923163848G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923165411G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923170934G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923172459G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923174022G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923175545G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923181108G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923182633G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923184156G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923185718G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923191242G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923192807G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923194330G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923195852G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923201414G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923202940G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190923204502G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz