APRS Packet Errors for EA5IVP (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
20251026223035	EA5IVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IVP-DP!3926.44N/000-27.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20251026230104	EA5IVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IVP-DP!3926.44N/000-27.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20251026233132	EA5IVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IVP-DP!3926.44N/000-27.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20251027000200	EA5IVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IVP-DP!3926.44N/000-27.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20251027003227	EA5IVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IVP-DP!3926.44N/000-27.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20251027010254	EA5IVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IVP-DP!3926.44N/000-27.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20251027013320	EA5IVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IVP-DP!3926.44N/000-27.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20251027030435	EA5IVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IVP-DP!3926.44N/000-27.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz
20251027040524	EA5IVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5IVP-DP!3926.44N/000-27.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.0000 MHz