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
20250916201415EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916201721EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916204458EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916204748EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916211552EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916211815EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916214648EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916214843EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916221736EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916221910EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916224820EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916224937EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916231859EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916232003EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250916234943EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250916235027EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250917002040EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250917002051EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250917005115EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250917005138EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250917012139EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250917012212EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz
20250917015204EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20250917015316EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 438.8000 MHz