APRS Packet Errors for G5BOB (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
20261014154154G5BOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G5BOB-DP!5203.72N/000-47.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20261014161352G5BOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G5BOB-DP!5203.72N/000-47.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20261014164548G5BOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G5BOB-DP!5203.72N/000-47.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20261014171744G5BOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G5BOB-DP!5203.72N/000-47.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20261014174939G5BOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G5BOB-DP!5203.72N/000-47.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20261014182132G5BOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G5BOB-DP!5203.72N/000-47.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20261014185327G5BOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G5BOB-DP!5203.72N/000-47.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20261014192523G5BOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G5BOB-DP!5203.72N/000-47.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20261014195718G5BOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G5BOB-DP!5203.72N/000-47.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20261014202912G5BOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G5BOB-DP!5203.72N/000-47.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz