APRS Packet Errors for EA1JBD (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
20191114181722EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114183244EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114184810EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114190334EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114191900EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114193423EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114194945EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114200509EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114202034EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114203557EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114205119EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114210639EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114212201EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114213721EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114215243EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114220804EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114222326EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114223845EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114225405EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114230924EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114232448EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114234006EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz
20191114235524EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1000@-7.6 MHz