APRS Packet Errors for DB0MOL (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
20260220045628DB0MOL>APMI04,SR3NJE*,qAR,SQ3RCH-3:@200730z5234.4N?y52*њrjz FO"Rela.ݹdr2[fe
20260220051645DB0MOL>APMI04,SR3NJE*,qAR,SQ3RCH-3:@200750z5334.48N/01s52.72Er439.200MHz O!rYZZ.׹bmonde
20260220053633DB0MOL>APMI04,SR3NJE*,qAR,SQ3RCH-3:@200810z5234.68N/0Lr*њrj!F] RY+́www.df0mol.Y
20260220055629DB0MOL>APMI04,SR3NJE*,qAR,SQ3RCH-3:@200830z5:4.48N/Lr*њrjz NM Zelai.db0[ˉY
20260220055629DB0MOL>APMI04,SR3NJE*,qAR,SQ3RCH-3:@200830z52.rrL*3;j! FM Rmlz.ww.d0}l.Y
20260220063636DB0MOL>APMI04,SR3NJE*,qAR,SQ3RCH-3:@200914z52&r0LM.72Gr439n200SjNm(Zeliksח0olY
20260220063637DB0MOL>APMI04,SR3NJE*,qAR,SQ3RCH-3:@200N2340132.?2Er439.200MHzH|>.www>dbˉ
20260220071632DB0MOL>APMI04,SR3NJE*,qAR,SQ3RCH-3:@2Lʪ0z=234.48N/01356*79IMHz F͐+is ߗ[l.d