APRS Packet Errors for EA5ISA (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
20191205111853EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205113409EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205114930EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205120447EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205122005EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205123523EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205125044EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205130603EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205132122EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205133641EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205135202EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205140720EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205142239EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205143758EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205145320EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205150839EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205152359EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205153919EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205155441EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205161000EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205162519EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205164040EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20191205165603EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz