APRS Packet Errors for PU2ROE (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
20240426152041PU2ROE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2ROE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 434.5000 MHz
20240426155119PU2ROE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2ROE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 434.5000 MHz
20240426165230PU2ROE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2ROE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 434.5000 MHz
20240426172306PU2ROE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2ROE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 434.5000 MHz
20240426175343PU2ROE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2ROE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 434.5000 MHz
20240426182419PU2ROE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2ROE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 434.5000 MHz
20240426185459PU2ROE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2ROE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 434.5000 MHz
20240426192536PU2ROE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2ROE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 434.5000 MHz
20240426195615PU2ROE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2ROE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 434.5000 MHz
20240426202653PU2ROE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2ROE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 434.5000 MHz