APRS Packet Errors for E22ZMG-9 (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
20220630035937E22ZMG-9>AESPT4,WIDE1-1,qAR,E22ZMG-1:!1849r*ʊzi:11aZҒj70kmh
20220630041347E22ZMG-9>AESPT4,WIDE1-1,qAR,E24CR-1:!1849.1rj+ )&
20220630050855E22ZMG-9>AESPT4,WIDE1-1,qAR,E22ZMG-1:!184)N011H
20220630051526E22ZMG-9>AESPT4,WIDE1-1,qAR,E22ZMG-3:!1848.53N/09M*09/010/A=001082
20220630061028E22ZMG-9>AESPT4,WIDE1-1,qAR,E24CR-1:!1847.76N/09.zzԚӫUY5:35 Max:75kmh
20220630061118E22ZMG-9>AESPT4,WIDE1-1,qAR,E23XBQ-1:!1847.98N/0jjLA1դ
20220630062551E22ZMG-9>AESPT4,WIDE1-1,qAR,E22ZMG-1:!1847.7Aª ʂ )
20220630065130E22ZMG-9>AESPT4,WIDE1-1,qAR,E22ZMG-3:!184)+LA=2j麉a Ҋj75kmh
20220630073011E22ZMG-9>AESPT4,WIDE1-1,qAR,E24CR-1:!1845.94N/09.zz
20220630075918E22ZMG-9>AESPT4,WIDE1-1,qAR,E24CR-1:!1850.19N/0992zzjJr N:24 Max:94kmh