APRS Packet Errors for EA5IOO (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
20251214093346	EA5IOO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IOO-DP!3837.52N/000-31.35rRNG0034 IPSC2-DVSPh-F MMDVM 430.4300 MHz
20251214100528	EA5IOO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IOO-DP!3837.52N/000-31.35rRNG0034 IPSC2-DVSPh-F MMDVM 430.4300 MHz
20251214103711	EA5IOO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IOO-DP!3837.52N/000-31.35rRNG0034 IPSC2-DVSPh-F MMDVM 430.4300 MHz
20251214110856	EA5IOO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IOO-DP!3837.52N/000-31.35rRNG0034 IPSC2-DVSPh-F MMDVM 430.4300 MHz
20251214114039	EA5IOO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IOO-DP!3837.52N/000-31.35rRNG0034 IPSC2-DVSPh-F MMDVM 430.4300 MHz
20251214121226	EA5IOO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IOO-DP!3837.52N/000-31.35rRNG0034 IPSC2-DVSPh-F MMDVM 430.4300 MHz
20251214124413	EA5IOO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IOO-DP!3837.52N/000-31.35rRNG0034 IPSC2-DVSPh-F MMDVM 430.4300 MHz
20251214131602	EA5IOO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IOO-DP!3837.52N/000-31.35rRNG0034 IPSC2-DVSPh-F MMDVM 430.4300 MHz
20251214134751	EA5IOO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IOO-DP!3837.52N/000-31.35rRNG0034 IPSC2-DVSPh-F MMDVM 430.4300 MHz
20251214141943	EA5IOO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IOO-DP!3837.52N/000-31.35rRNG0034 IPSC2-DVSPh-F MMDVM 430.4300 MHz