APRS Packet Errors for EA5IHJ (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
20181018015035EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018020553EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018022110EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018023632EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018025149EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018030707EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018032224EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018033744EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018035302EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018040824EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018042341EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018043901EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018045419EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018050943EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018052501EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018054022EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018055541EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018061058EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018062616EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018064137EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018065703EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018071222EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz
20181018072748EA5IHJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IHJ-DP!3822.90N/000-46.01rRNG0034 IPSC2-EA-Hotspot MMDVM 438.2250@-7.6 MHz