APRS Packet Errors for EA5GVP (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
20250918083751EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250918090842EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250918093921EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250918100958EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250918104032EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250918111117EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250918114202EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250918121240EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250918141606EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz