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
20181218194747EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218200319EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218201850EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218203414EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218204946EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218210511EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218212032EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218213604EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218215125EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218220649EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218222210EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218223729EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218225250EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218230814EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218232337EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218233857EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181218235415EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181219000941EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181219002458EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181219004016EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181219005532EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181219011051EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181219012607EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz
20181219014123EA1JBD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1JBD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.2250@-7.6 MHz