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
20190916152440G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916154002G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916155522G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916161042G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916162601G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916164807G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916170327G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916171846G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916173405G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916174926G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916180444G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916182003G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916183522G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916185044G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916190603G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916192121G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916193640G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916195203G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916200719G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916202236G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916203753G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916205313G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190916210832G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz