APRS Packet Errors for PY4CH-15 (last 24 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
20250711114031PY4CH-15>APRS,qAR,PY4WVZ:!1944nÓÓõ‚¢šª‚r¢Šº C¨ªª‚åÑchcarlos@gmail.com
20250711132711PY4CH-15>APRS,qAR,PY4WVZ:!1944>Óš½04350.41W# (%5‚åÑchcarlos@gmail.com
20250711144542PY4CH-15>APRS,qAR,PY4BR-10:!1N“©ºš½04350.4L5
20250711144542PY4CH-15>APRS,qAR,PY4WVZ:!1N“©ºš½04350.4L5AIMÅ py4chgØ.ëkµ…¥±¹com
20250711144820PY4CH-15>APRS,qAR,PY4BR-10:!1944.57S/04350.41_$
20250711163503PY4CH-15>APRS,qAR,PY4BR-10:!19ttŸMÓõ‚¢šª‚r¢Šº`APRS1 py4chcaòlïs@gmail.com
20250711194142PY4CH-15>APRS,APRS,WIDE1-1,qAR,PY4BR-10:!1944.57S/043Mr¢Šº APRS1 py4chcarlos@gmail.com
20250711194146PY4CH-15>APRS,APRS,PY4AC-15,WIDE1*,qAR,PY4WVZ:!1944.MM½043Mr¢Šº APRSL‚åÑchcarlos@gmail.com