APRS Packet Errors for M0JIW (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
20251014033337M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014040500M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014043647M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014050823M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014054000M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014061138M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014064318M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014071457M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014074650M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014081832M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014085027M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014092158M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014095346M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014102534M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014105735M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014112910M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014120100M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014123251M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014130451M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014133638M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014140840M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014144043M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014151218M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014154409M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251014171914M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz