APRS Packet Errors for PU2SFZ (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
20250716171806	PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250716174823	PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250716181841	PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250716184858	PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250716191915	PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250716194931	PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250716201950	PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250716215042	PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz
20250716222100	PU2SFZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU2SFZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-BRAZIL MMDVM 439.3500 MHz