APRS Packet Errors for PY4KD (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
20191115103450PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115105008PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115110532PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115112052PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115113619PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115115134PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115120652PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115122206PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115123732PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115125248PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115130804PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115132320PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115133845PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115135402PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115140923PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115142438PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115144005PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115145530PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115151050PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115152612PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115154144PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191115155709PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!0000.00N/-2500.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz