APRS Packet Errors for GM3AND-DP (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
20260208150245GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.26N/00246.29WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208150352GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz
20260208153402GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz
20260208153455GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.26N/00246.29WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208160413GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz
20260208160705GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.26N/00246.29WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208163424GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz
20260208163914GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.26N/00246.29WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208170435GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz
20260208171121GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.26N/00246.29WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208173446GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz
20260208174330GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.26N/00246.29WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208180457GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz
20260208181539GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.26N/00246.29WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208183509GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz
20260208184746GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.26N/00246.29WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208190520GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz
20260208191951GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.26N/00246.29WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208193531GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz
20260208195155GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.26N/00246.29WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208200542GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz
20260208202357GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.26N/00246.29WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208203553GM3AND>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3AND-DP!5612.00N/00246.20WrRNG0034 IPSC2-DVSPh-D MMDVM 434.4000 MHz