APRS Packet Errors for EB1HHA (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
20191206041648EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206043159EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206044708EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206050216EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206051725EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206053237EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206054745EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206060254EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206061803EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206063314EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206064823EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206070332EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206071840EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206073352EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206074901EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206080410EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206081920EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206083433EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206084943EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206090454EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206092005EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206093521EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206095036EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz
20191206100548EB1HHA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1HHA-DP!4331.17N/-05-39.84rRNG0034 IPSC2-EA1Master MMDVM 434.0000 MHz