APRS Packet Errors for EA4FFX (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
20250121074819	EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4022.20N/004-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125 MHz
20250121081853	EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4022.20N/004-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125 MHz
20250121084926	EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4022.20N/004-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125 MHz
20250121092000	EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4022.20N/004-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125 MHz
20250121095036	EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4022.20N/004-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125 MHz
20250121102111	EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4022.20N/004-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125 MHz
20250121105147	EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4022.20N/004-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125 MHz
20250121112222	EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4022.20N/004-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125 MHz
20250121115257	EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4022.20N/004-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125 MHz