APRS Packet Errors for EA1FG (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
20191117094640EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117100157EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117101715EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117103235EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117104754EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117110313EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117111830EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117113351EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117114909EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117120426EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117121945EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117123506EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117125023EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117130541EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117132059EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117133619EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117135137EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117140654EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117142211EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117143730EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117145247EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117150804EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117152321EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz
20191117153841EA1FG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1FG-DP!4321.37N/-08-27.27rRNG0034 IPSC2-EA-Hotspot MMDVM 431.0000 MHz