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
20260311073006PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260311083135PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260311090221PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260311093305PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260311100353PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260311103438PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260311110527PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260311113614PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260311120704PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz
20260311123752PU1PWE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1PWE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 433.0000 MHz