APRS Packet Errors for GB3IN (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
20250912061214	GB3IN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3IN-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-D MMDVM 444.0000@+5.0 MHz
20250912064224	GB3IN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3IN-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-D MMDVM 444.0000@+5.0 MHz
20250912081254	GB3IN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3IN-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-D MMDVM 444.0000@+5.0 MHz
20250912091314	GB3IN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3IN-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-D MMDVM 444.0000@+5.0 MHz
20250912101334	GB3IN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3IN-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-D MMDVM 444.0000@+5.0 MHz
20250912111354	GB3IN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3IN-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-D MMDVM 444.0000@+5.0 MHz
20250912114404	GB3IN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3IN-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-D MMDVM 444.0000@+5.0 MHz