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
20190922060508EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922062025EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922063542EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922065059EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922070620EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922072141EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922073659EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922075219EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922080741EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922082301EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922083822EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922085344EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922090908EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922092429EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922093950EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922095513EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922101038EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922102559EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922104122EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922105645EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922111211EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922112733EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922114256EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz
20190922115819EA5ISA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ISA-DP!3925.33N/000-23.26rRNG0034 IPSC2-EA-Hotspot MMDVM 434.4248 MHz