APRS Packet Errors for OE3MJA (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
20260612150704	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20260612153741	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20260612160819	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20260612163858	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20260612170940	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20260612174018	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20260612181057	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20260612184133	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20260612191209	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20260612194245	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz