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
20251215124531KD2AYD-3>APN383,qAR,KB2LUV-1:!42u6.73NS07601.65W#ÐHG6800 W2 Wilderness SAR Team
20251215131327KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73ÎS07601.65W#PHG6800
20251215142327KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601>>5W#PHG6800
20251215150327KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS0?601.v5W#PHG6800
20251215151327KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.6uW#PHG6800
20251215153531KD2AYD-3>APN383,qAR,KB2LUV-1:!42=6.73NS07601.65W#PHG6800 W2 Wilderness SAR Team
20251215163327KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73ÎS07601.65W#PHG6800
20251215174327KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.?sNS07601.65W#PHG6800
20251215175719KD2AYD-3>APN383,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4256.73NS07601.65×#PHG6x00
20251215181121KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601>65W#PHG6800 W2 Wilderness SAR Team
20251215181534KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.>5W#PHG6800 W2 Wilderness SAR Team
20251215182327KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.65×#PHG6800