APRS Packet Errors for OE3HPT (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
20240427235055OE3HPT>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3HPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.7000 MHz
20240428002125OE3HPT>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3HPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.7000 MHz
20240428005154OE3HPT>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3HPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.7000 MHz
20240428012225OE3HPT>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3HPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.7000 MHz
20240428015258OE3HPT>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3HPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.7000 MHz
20240428022329OE3HPT>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3HPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.7000 MHz
20240428025401OE3HPT>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3HPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.7000 MHz
20240428032432OE3HPT>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3HPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.7000 MHz
20240428035501OE3HPT>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3HPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.7000 MHz
20240428042531OE3HPT>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3HPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.7000 MHz