APRS Packet Errors for G7ELZ (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
20250918040843G7ELZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7ELZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6000 MHz
20250918044029G7ELZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7ELZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6000 MHz
20250918051231G7ELZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7ELZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6000 MHz
20250918054433G7ELZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7ELZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6000 MHz
20250918061610G7ELZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7ELZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6000 MHz
20250918071953G7ELZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7ELZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6000 MHz
20250918075147G7ELZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7ELZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6000 MHz
20250918082329G7ELZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7ELZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6000 MHz
20250918085527G7ELZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7ELZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6000 MHz
20250918092715G7ELZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7ELZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.6000 MHz