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
20250509113517EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509113624EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250509120542EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509120648EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250509123607EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509123710EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250509130631EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509130743EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250509133656EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509133816EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250509140721EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509140839EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250509143745EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509143902EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250509150810EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509150925EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250509153834EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509153959EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250509160859EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509161023EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250509163923EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509164056EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz
20250509170948EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.96N/000-9.98ErRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20250509171121EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.86ErRNG0034 IPSC2-EA4Master MMDVM 435.2000 MHz