APRS Packet Errors for M0INR (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
20190218031829M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218033511M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218035152M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218040830M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218042503M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218044135M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218045806M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218051436M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218053109M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218054744M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218060418M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218062053M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218063724M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218065357M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218071029M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218072703M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218074333M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218080009M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218081640M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218083312M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218084947M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218090622M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz