APRS Packet Errors for EA5KV (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
20251224112544EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224114406EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251224115626EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224121437EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251224122657EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224124506EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251224125726EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224131536EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251224132802EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224134606EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251224135856EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224141637EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251224143010EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224144706EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251224150058EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224151736EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251224153127EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224154808EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251224160158EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224161841EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251224163228EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224164913EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251224170257EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20251224171943EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz