APRS Packet Errors for OE5GNB (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
20250917140929	OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250917151052	OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250917154133	OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250917161214	OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250917164255	OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250917171336	OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250917174416	OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250917181459	OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250917184540	OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz
20250917191619	OE5GNB>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE5GNB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 435.0000 MHz