APRS Packet Errors for MI0RWY (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
20260329164123	MI0RWY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MI0RWY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6625 MHz
20260329174618	MI0RWY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MI0RWY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6625 MHz
20260329181948	MI0RWY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MI0RWY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6625 MHz
20260329185117	MI0RWY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MI0RWY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6625 MHz
20260329192340	MI0RWY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MI0RWY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6625 MHz
20260329195601	MI0RWY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MI0RWY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6625 MHz
20260329202818	MI0RWY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MI0RWY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6625 MHz
20260329210033	MI0RWY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MI0RWY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6625 MHz
20260329213243	MI0RWY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MI0RWY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6625 MHz
20260329220450	MI0RWY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MI0RWY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6625 MHz