APRS Packet Errors for OE3MJA (last 24 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
20261024152246	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20261024155316	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20261024162348	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20261024165417	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20261024172449	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20261024175519	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20261024182549	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20261024185616	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20261024192643	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz
20261024195709	OE3MJA>APZDMR,QTH,TCPIP*,qAU,HAMCLOUD3:)OE3MJA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-OE-DMO MMDVM 433.5000 MHz