APRS Packet Errors for EB5FVH (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
20260425140853	EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20260425143926	EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20260425150958	EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20260425154029	EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20260425161102	EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20260425164134	EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20260425171209	EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20260425174240	EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20260425181314	EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz