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
20190218170714M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218172353M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218174024M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218175658M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218181331M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218183014M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218184649M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218190324M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218191956M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218193631M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218195303M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218200938M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218202611M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218204241M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218205913M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218211546M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218213219M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218214851M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218220522M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218222156M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190218223827M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz