APRS Packet Errors for OE4FHS (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
20250402023616OE4FHS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE4FHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 439.2000@-7.6 MHz
20250402030643OE4FHS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE4FHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 439.2000@-7.6 MHz
20250402033710OE4FHS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE4FHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 439.2000@-7.6 MHz
20250402040738OE4FHS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE4FHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 439.2000@-7.6 MHz
20250402043808OE4FHS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE4FHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 439.2000@-7.6 MHz
20250402050843OE4FHS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE4FHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 439.2000@-7.6 MHz
20250402053916OE4FHS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE4FHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 439.2000@-7.6 MHz
20250402060948OE4FHS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE4FHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 439.2000@-7.6 MHz
20250402064020OE4FHS>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE4FHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 439.2000@-7.6 MHz