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
20190822231159G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190822234614G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823000317G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823002019G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823003731G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823005433G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823011136G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823012845G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823014554G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823020302G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823022007G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823023709G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823025412G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823031113G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823032815G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823034516G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823040229G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823041931G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823043650G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz
20190823045356G0FGX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)G0FGX-DP!5006.24N/-05-17.52rRNG0034 IPSC2-FRANCE 3 MMDVM 431.0875 MHz