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
20260318184514KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS0w601.65W#PHG6800
20260318190514KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.v5W#PHG6800
20260318194307KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS0760q.65W#PHG6800 W2 Wilderness SAR Tåam
20260318195514KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.65×#PHG6800
20260318195719KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.65×#PHG6800 W2 Wilderness SAR Team
20260318200514KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.65_#PHG6800
20260318200906KD2AYD-3>APN383,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4256.73NS0w601.65W#PHG6800
20260318210906KD2AYD-3>APN383,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!42=6.73NS07601.65W#PHÇ6800
20260318212308KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.65×#PHG6800 W2 Wilderness SAR Tea}
20260318231719KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.6uW#PHG6800 W2 Wilderness SAR Team
20260318235720KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.65_#PHG6800 W2 Wilderness SAR Team