APRS Packet Errors for HS0QKD-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
20250124182030HS0QKD-2>APEZT1-1,E21SMM-3*,qAR,E24MSQ-13:!1304.95N/L⻻rռ*EzTNC Aprs indy D-Star byHS0QKD PHG2280
20250124182037HS0QKD-2>APEZT1-1,HS7AM-10*,qAR,E24MSQ-13:!1304.95N/10ªªr’º*EzTNC Aprs indy D-Star byHS0QKD PHG™&‚
20250124184634HS0QKD-2>APEZT1-1,WIDE1-1,qAR,E24MSQ-13:!1304.95N/10055.2·Q¤”Q9Aprs indy D-Star byHS0QKD PHG2280
20250124200520HS0QKD-2>APEZT1-1,WIDE1-1,qAR,E24MSQ-13:!1304.95N/10ªªr’º*EzTNC Aprs indy D-Star byHS0QKD PHG2280
20250124212249HS0QKD-2>APEZT1-1,WIDE1-1,qAR,HS1AL-1:!130š)ªr½10055.27E#EzTNC Aprs indy D-Star byjŠ-PHG22œ
20250124214845HS0QKD-2>APEZT1-1,WIDE1-1,qAR,HS1AL-1:!1304.95N/1005MIº*EzTNC Aprs indy D-Star byHS0QKD PHG2280
20250124214845HS0QKD-2>APEZT1-1,WIDE1-1,qAR,HS1AL-1:!1304.95N/1005MI�*�EzTNC Aprs indy D-Star byHS0QKD PHG2280
20250124214847HS0QKD-2>APEZT1-1,HS5NMF*,qAR,HS1AL-1:!1304.95N/10055.™SÔ*éQ9Aprs indy D-Star byHS0QKD PHG2280
20250124214847HS0QKD-2>APEZT1-1,HS5NMF*,qAR,HS1AL-1:!1304.95N/10055.�S�*�Q9�Aprs indy D-Star byHS0QKD PHG2280