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
20250916085711EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916090546EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916092748EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916093617EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916100648EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916102922EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916103718EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916110003EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916110750EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916113100EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916113821EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916120200EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916120854EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916123247EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916123925EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916130336EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916130956EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916133428EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916134027EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916140512EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916141100EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916143605EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916144129EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz