APRS Packet Errors for PU2SFZ (last 24 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
20250826182152PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250826185211PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250826192229PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250826195247PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250826202305PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250826205322PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250826212339PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250826215357PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250826222415PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250826225433PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250826232450PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250826235508PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827002525PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827005543PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827012600PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827015617PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827022633PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827133246PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827140305PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827143322PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827150340PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827153357PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827170452PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827173509PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250827180527PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz