APRS Packet Errors for N3HYM (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
20191208001934N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208003443N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208004952N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208010501N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208012014N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208013523N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208015032N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208020541N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208022052N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208023600N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208025110N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208030619N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208032130N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208033639N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208035148N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208040657N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208042211N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208043720N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208045229N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208050738N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208052249N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208053757N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz
20191208055305N3HYM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3HYM-DP!3925.49N/-77-30.22rRNG0034 IPSC2-EA1Master MMDVM 433.5000 MHz