APRS Packet Errors for MM1AVR (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
20190419183046MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419184747MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419190509MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419192209MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419193916MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419195619MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419201316MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419203015MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419204721MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419210422MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419212120MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419213820MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419215523MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419221226MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419222926MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419224630MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419230326MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419232020MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419233714MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190419235407MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz
20190420001102MM1AVR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MM1AVR-DP!5623.92N/-05-28.54rRNG0034 IPSC2-Scotland MMDVM 438.8000 MHz