APRS Packet Errors for EB3FMU (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
20260828143018EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20260828144122EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20260828150108EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20260828151148EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20260828153133EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20260828154213EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20260828161239EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz
20260828163248EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20260828164304EB3FMU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3FMU-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.4500 MHz