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
20190217150830M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217152510M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217154147M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217155832M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217161508M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217163142M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217164815M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217170501M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217172133M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217173816M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217175451M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217181122M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217182757M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217184438M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217190131M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217191820M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217193504M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217195147M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217200817M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217202451M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz
20190217204123M0INR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0INR-DP!5228.48N/-01-46.11rRNG0034 IPSC2-Scotland MMDVM 432.8000 MHz