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
20251015090918E22ZMG-9>AESPT4,WIDE1-1,qAR,E22ZMG-3:!1œ“r¢’r½09901.60E>237/015/A=001010
20251015091015E22ZMG-9>AESPT4,WIDE1-1,qAR,E24CR-1:!1842.23N/09901—&S”ŠªÂz‚Š’zõ000967 DC:12.07V DX:46km Uptime:09:14 Topspeed:109kmh SAT:20 HDOP:0.7
20251015093506E22ZMG-9>AESPT4,WIDE1-1,qAR,E24CR-1:!1843.30N/09902.4*ù346/025/A=000958 DC:12.25V DX:49km Uptime:09:39 Topspeed:109kmh SAT:22 HDOP:0.6
20251015093840E22ZMG-9>AESPT4,HS5HBQ-2*,qAR,E22ZMG-10:!1845.24Š&Óz‚šLÊ¢¢"L&"a麙N&¢Í©Æ E¥é
20251015094106E22ZMG-9>AESPT4,WIDE1-1,qAR,E24CR-1:!1846—Nr½09901.61E>352/038/A=000958
20251015100424E22ZMG-9>AESPT4,WIDE1-1,qAR,E24CR-1:!1853.25N/09900.78 LŠ‚’‚
20251015100657E22ZMG-9>AESPT4,WIDE1-1,qAR,E23XBQ-1:!1853.98N/09900—¦*ù331/027/A=001007
20251015101150E22ZMG-9>AESPT4,WIDE1-1,qAR,HS5HBQ-2:!1855ÕNå8¹37Íz‚¢)&˜LDÅÅ7a¢Z©««&LM¢½ÁÍÁ••‘é109kmh SAT:22 HDOP:0.6
20251015101258E22ZMG-9>AESPT4,WIDE1-1,qAR,E23XBQ-1:!1856.62N/0NªÊr‚²*ù344/042/A=001046 DC:13.17V DX:75km Uptime:10:17 Topspeed:109kmh SAT:21 HDOP:0.6
20251015104019E22ZMG-9>AESPT4,WIDE1-1,qAR,HS5HBQ-2:!1902Á‚ʪ ’‚š š)‚ÂÊj)¥Ó««§õÁÍÁ••‘é109kmh SAT:22 HDOP:0.6