APRS Packet Errors for GM4AUP (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
20250702102109	GM4AUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM4AUP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 430.0750@+9.0 MHz
20250702105307	GM4AUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM4AUP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 430.0750@+9.0 MHz
20250702112445	GM4AUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM4AUP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 430.0750@+9.0 MHz
20250702115700	GM4AUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM4AUP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 430.0750@+9.0 MHz
20250702122839	GM4AUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM4AUP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 430.0750@+9.0 MHz
20250702130038	GM4AUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM4AUP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 430.0750@+9.0 MHz
20250702133255	GM4AUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM4AUP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 430.0750@+9.0 MHz
20250702140513	GM4AUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM4AUP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 430.0750@+9.0 MHz
20250702143749	GM4AUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM4AUP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 430.0750@+9.0 MHz