APRS Packet Errors for EA1DZR (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
20191117133157EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117134708EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117140218EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117141727EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117143240EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117144750EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117150300EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117151810EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117153323EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117154833EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117160345EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117161855EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117163408EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117164919EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117170429EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117171939EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117173451EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117175001EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117180512EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117182023EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117183536EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117185046EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117190556EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz
20191117192106EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 433.0000 MHz