APRS Packet Errors for OE3YHC-DP (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
20260209092808	OE3YHC>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3YHC-DP!4843.74N/01452.50ErRNG0034 IPSC2-OE-DMO MMDVM 434.7500 MHz
20260209095843	OE3YHC>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3YHC-DP!4843.74N/01452.50ErRNG0034 IPSC2-OE-DMO MMDVM 434.7500 MHz
20260209102918	OE3YHC>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3YHC-DP!4843.74N/01452.50ErRNG0034 IPSC2-OE-DMO MMDVM 434.7500 MHz
20260209105952	OE3YHC>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3YHC-DP!4843.74N/01452.50ErRNG0034 IPSC2-OE-DMO MMDVM 434.7500 MHz
20260209113027	OE3YHC>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3YHC-DP!4843.74N/01452.50ErRNG0034 IPSC2-OE-DMO MMDVM 434.7500 MHz
20260209123136	OE3YHC>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3YHC-DP!4843.74N/01452.50ErRNG0034 IPSC2-OE-DMO MMDVM 434.7500 MHz
20260209130211	OE3YHC>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3YHC-DP!4843.74N/01452.50ErRNG0034 IPSC2-OE-DMO MMDVM 434.7500 MHz
20260209133245	OE3YHC>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3YHC-DP!4843.74N/01452.50ErRNG0034 IPSC2-OE-DMO MMDVM 434.7500 MHz
20260209140320	OE3YHC>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3YHC-DP!4843.74N/01452.50ErRNG0034 IPSC2-OE-DMO MMDVM 434.7500 MHz
20260209143355	OE3YHC>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3YHC-DP!4843.74N/01452.50ErRNG0034 IPSC2-OE-DMO MMDVM 434.7500 MHz