APRS Packet Errors for KF2R (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
20250314163112KF2R>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KF2R-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250314170147KF2R>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KF2R-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250314173221KF2R>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KF2R-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250314180256KF2R>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KF2R-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250314183332KF2R>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KF2R-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250314190407KF2R>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KF2R-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250314193442KF2R>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KF2R-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250314200519KF2R>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KF2R-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250314203551KF2R>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KF2R-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250314213655KF2R>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KF2R-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz