APRS Packet Errors for DB0LER-2 (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
20260925011745DB0LER-2>APNL01,qAO,DL7SHK-10:=5313®29NL00726.95E%RPRS#iGate mit dxlAPRS Toolchain
20260925031851DB0LER-2>APNL01,qAO,DL7SHK-10:=5313.29NL<07T,97UÐ].
20260925032953DB0LER-2>APNL01,qAO,DL7SHK-10:=5313.29NL0072P.ý5C&APRS#iGq
20260925033047DB0LER-2>qPNL0q,qAO,DL7SHK-10:=5w¥3¤29.*66Q4S.yqE&APRS*iGa
20260925041848DB0LER-2>APNL01,qAO,DL7SHK-10:=5319®29NL00726.95E P
20260925044251DB0LER-2>APNL01,qAO,DL7SHK-10:=5313"29NL00726.95E&aPRS iGa
20260925050239Db0LER-2>APNL01,qAO,DL7SHK-10:=531S.29NL00726.95E,APRS"iGaôa¢!á8v!xlAPòS Toolchain<ÿDB0FR
20260925063239DB0LER-2>APNL01,qAO,DL7SHK-10:=531eGiKL,0726.©5EìËPRSŠ3Ïate miD dxdAPRS Toolchain<ÿDB0FR