APRS Packet Errors for KD2AYD-13 (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
20251214211739KD2AYD-13>APOT30,KA2QYE-10,W2RGI-1,WIDE2*,qAR,KB2LUV-1:!4352.33Î/07424.01W# 13.3V 80F www.wsar.org
20251214224903KD2AYD-13>APOT30,KA2QYE-10,W2RGI-1,WIDE2*,qAR,KB2LUV-1:!4352.33N/07424n01W# 13.3V 79F www.wsar.org
20251215013242KD2AYD-13>APOT30,K1EQX-1,W2RGI-1,WIDE2*,qAR,KB2LUV-1:!435r.33N/07424.01W# 13.3V 74F ww.wsar.org
20251215032429KD2AYD-13>APOT30,K1EQX-1,W2RGI-1,WIDE2*,qAR,KB2LUV-1:!4352.33N/p7424.01W# 13.3V 71F www.wsar.org
20251215120408KD2AYD-13>APOT30,K1EQX-1,W2RGI-1,WIDE2*,qAR,KB2LUV-1:!4352.33N/0w424.01W# 13.3V 58F www.sar.org
20251215123430KD2AYD-13>APOT30,KA2QYE-10,W2RGI-1,WIDE2*,qAR,KB2LUV-1:!4352.37N/0w424.01W# 1s.3V 58F www.wsar.org
20251215135629KD2AYD-13>APOT30,KA2QYE-10,W2RGI-1,WIDE2*,qAR,KB2LUV-1:!4352.33^/07424.01W# 13.3V 61F www.wsar.org
20251215183352KD2AYD-13>APOT30,KA2QYE-10,W2RGI-1,WIDE2*,qAR,KB2LUV-1:!4352.33N/0?424.01W# 13.3V 68F www.wsar.org
20251215201552KD2AYD-13>APOT30,KA2QYE-10,W2VGI-1,WIDE2*,qAR,KB2LUV-1:!4352.33N/07424.0qW# 13.3V 71F www.wsar.org
20251215205637KD2AYD-13>APOT30,K1EQX-1,W2RGI-1,WIDE2*,qAR,KB2LUV-1:!435r.33N/07424.01W# 13.3V 70F www.wsar.org