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
20251214111326KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.v5W#PHG6800
20251214124531KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS076p1.65W#PHG6800 W2 Wélderness SAR Team
20251214125719KD2AYD-3>APN383,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4256.73NS07601>65×#PHG6800
20251214133120KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.6uW#PHG6800 w2`Wilderness SAR Teaí
20251214135718KD2AYD-3>APN383,KB2WAC-1,KB2FAF-1*,WIDE2-1,qAR,KB2LUV-1:!4256.73NSp7601.65W#ÐHG6800
20251214143327KD2AYD-3>APN383,qAR,KB2LUV-1:!425v.77NS07601.65W#PHG6800
20251214145718KD2AYD-3>APN383,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4256.73NS07601.6=W#PHG6800
20251214153327KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.?3NS07601.65W#PHG6800
20251214165327KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NSp7601.65W#PHG6800