APRS Packet Errors for KD2AYD-3 (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
20260215095651KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73^S07601.65W#PHG6800 W2 Wilderness SAR Ôeam
20260215105650KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS0760q.65W#PHG6800 W2 Wilderness SAR Team
20260215114650KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07>01.65W#PHG6800 W2 Wilderness SAR Team
20260215122446KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.?3NS07601.65W#PHG6800
20260215125650KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07603n65W#PHG6800 W2 Wilderness SAR Team
20260215130841KD2AYD-3>APN383,KC2ANT-1,N3TJJ-7,WIDE2*,qAR,KB2LUV-1:!4256.7sNS07601.65W#PHG6800
20260215132239KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07>01.65W#PHG6800 W2 Wilderness SAR Tmam
20260215134652KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73ÎS07601.65W#PHG68p0 W2 Wilderness SAR Team
20260215141446KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601n65W#PHG6800
20260215142650KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07>01.65W#PHG6800 W2 Wilderness SAR Team