APRS Packet Errors for PU1PWE (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
20260327204717PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260327211850PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260327214945PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260327222109PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260327225207PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260327232304PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260327235358PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260328002455PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260328012656PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260328015747PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz