APRS Packet Errors for EB4FOG (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
20250918004237	EB4FOG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB4FOG-DP!0800.00N/080-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 444.0000@+5.0 MHz
20250918011303	EB4FOG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB4FOG-DP!0800.00N/080-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 444.0000@+5.0 MHz
20250918014331	EB4FOG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB4FOG-DP!0800.00N/080-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 444.0000@+5.0 MHz
20250918021359	EB4FOG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB4FOG-DP!0800.00N/080-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 444.0000@+5.0 MHz
20250918024426	EB4FOG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB4FOG-DP!0800.00N/080-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 444.0000@+5.0 MHz
20250918031452	EB4FOG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB4FOG-DP!0800.00N/080-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 444.0000@+5.0 MHz
20250918034518	EB4FOG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB4FOG-DP!0800.00N/080-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 444.0000@+5.0 MHz
20250918041545	EB4FOG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB4FOG-DP!0800.00N/080-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 444.0000@+5.0 MHz
20250918044612	EB4FOG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB4FOG-DP!0800.00N/080-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 444.0000@+5.0 MHz