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
20191017230133PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191017231652PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191017233218PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191017234734PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018000255PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018001811PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018003340PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018004855PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018010415PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018011934PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018013458PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018015012PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018020536PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018022050PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018023615PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018025135PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018030651PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018032208PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018033731PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018035245PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018040802PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018042317PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018043842PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz
20191018045357PY4KD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PY4KD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-BRAZIL MMDVM 433.1250 MHz