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
20190423162523EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423164209EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423165907EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423171603EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423173256EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423174942EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423180626EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423182308EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423183950EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423185630EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423191308EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423192947EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423194630EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423200314EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423202010EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423203654EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190423205337EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.48N/-05-40.00rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz