APRS Packet Errors for EA2COE (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
20190722173012EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722174737EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722180456EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722182212EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722183915EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722185614EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722191330EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722193044EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722194808EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722200514EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722202216EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722203930EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722205643EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722211340EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722213032EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722214729EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190722222121EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz