APRS Packet Errors for EA4DNO (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
20190620033525EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620035210EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620040856EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620042540EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620044226EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620045915EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620051559EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620053245EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620054929EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620060621EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620062305EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620063954EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620065644EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620071339EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620073033EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620074738EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620080436EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620082136EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620083849EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620085544EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz
20190620091242EA4DNO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DNO-DP!3852.11N/-06-49.03rRNG0034 IPSC2-EA4Master MMDVM 144.8750 MHz