APRS Packet Errors for EB3FMU (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
20201022084924EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2BIO:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20201022102521EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2BIO:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20201022105724EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2BIO:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20201022112929EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2BIO:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20201022120130EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2BIO:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20201022123337EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2BIO:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20201022130524EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2BIO:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20201022133723EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2BIO:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20201022140922EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2BIO:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20201022144123EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2BIO:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz