APRS Packet Errors for PY1JHG (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
20190116112234PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116113902PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116115524PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116121330PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116122955PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116124619PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116130233PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116131904PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116133518PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116135132PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116140739PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116142400PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116144021PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116145636PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116151257PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116152904PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116154602PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116160327PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116162105PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116163820PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116165516PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!0000.00N/00000.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz
20190116171312PY1JHG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY1JHG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 439.5500@-5.0 MHz