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
20190818140024G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818141726G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818143449G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818145155G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818150902G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818152603G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818154309G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818160010G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818161711G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818163415G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818165114G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818170816G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818172517G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818174219G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818175923G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818181629G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818183330G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818185029G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818190732G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818192436G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190818194135G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz