APRS Packet Errors for EA7ERD (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
20190217214830EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217220501EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217222136EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217223810EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217225458EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217231130EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217232800EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217234429EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218000056EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218001719EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218003343EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218005010EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218010638EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218012303EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218013925EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218015553EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218021225EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218022849EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218024520EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218030150EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218031818EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190218033442EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz