APRS Packet Errors for DO3GB-11 (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
20250411154510DO3GB-11>APRS,qAO,DF1GD-10:!/6$>6PKlv_b"H.../...g...tnanr...p...P...h00b.....Bernd mobiel 144.650Mhz
20250411161209DO3GB-11>APRS,qAO,DF1GD-10:!/6$>:PKl{_W3H.../...g...tnanr...p...P...h00b.....Bernd mobiel 144.650Mhz
20250411161306DO3GB-11>APRS,qAO,DF1GD-10:!/6$=qPKm/_%0H.../...g...tnanr...p...P...h00b.....Bernd mobiel 144.650Mhz
20250411164146DO3GB-11>APRS,qAO,DF1GD-10:!/6$=pPKmM_g#H.../...g...tnanr...p...P...h00b.....Bernd mobiel 144.650Mhz
20250411170128DO3GB-11>APRS,qAO,DF1GD-10:!/6$
20250411170538DO3GB-11>APRS,qAO,DF1GD-10:!/6$?BPKl{_`9H.../...g...tnanr...p...P...h00b.....Bernd mobiel 144.650Mhz
20250411170824DO3GB-11>APRS,qAO,DF1GD-10:!/6$=lPKm9_&%H.../...g...tnanr...p...P...h00b.....Bernd mobiel 144.650Mhz
20250411172729DO3GB-11>APRS,qAO,DF1GD-10:!/6$=lPKm*_2(H.../...g...tnanr...p...P...h00b.....Bernd mobiel 144.650Mhz
20250411190318DO3GB-11>APRS,qAO,DF1GD-10:!/6$={PKm@_2#H.../...g...tnanr...p...P...h00b.....Bernd mobiel 144.650Mhz
20250411190519DO3GB-11>APRS,qAO,DF1GD-10:!/6$?(PKm/_2&H.../...g...tnanr...p...P...h00b.....Bernd mobiel 144.650Mhz
20250411190848DO3GB-11>APRS,qAO,DF1GD-10:!/6$>NPKm(_P/H.../...g...tnanr...p...P...h00b.....Bernd mobiel 144.650Mhz