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
20251118043510KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS0?601.65w#PHG6800 W2 Wilderness SAR Team
20251118060059KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS076p1.65W#PHÇ6800 W2 Wilderness SAR Team
20251118061306KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS0760q.65W#PHG6800
20251118063510KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601>65W#PHG6800 W2 Wilderness SAR Team
20251118065656KD2AYD-3>APN383,WIDE2-2,qAR,KB2LUV-1:!4256.73NS07601.65×#PHG6800
20251118085658KD2AYD-3>APN383,KC2ANT-1,AD3O-3,WIDE2*,qAR,KB2LUV-1:!4256.73NS07601.6=W#PHG>800
20251118092306KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73ÎS07601.65W#PHG6800
20251118095656KD2AYD-3>APN383,WIDE2-2,qAR,KB2LUV-1:!4256>73NS07601.65W#PHG6800
20251118100059KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NÓ07601>65W#PHG6800 W2 Wilderness SAR Team