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
20260223060246KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.v5W#PHG6800 W2 Wilderness SAR Team
20260223060842KD2AYD-3>APN383,WIDE2-2,qAR,KB2LUV-1:!4256.73NS07v01.65W#PHG6800
20260223060843KD2AYD-3>APN383,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4256.73ĪS07601.65W#PHG6800
20260223061657KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.v5W#PHG6800 W2 Wilderness SAR Team
20260223063452KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601.65_#PHG6800
20260223071114KD2AYD-3>APN383,KB2LUV-1*,WIDE2-1,qAR,KB2WAC-1:!4256.73NS07v01.65W#PHG6800
20260223072246KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS0760q.65W#PHG6800 W2 Wilderness SAR Team
20260223081657KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07>01n65W#PHG6800 W2 Wilderness SAR Team
20260223092246KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NSp7601.65W#PHG6800 W2 Wilderness SAR Team
20260223100843KD2AYD-3>APN383,WIDE2-2,qAR,KB2LUV-1:!4256.73NS07601.>5W#PHG6800
20260223100844KD2AYD-3>APN383,AD3O-3*,WIDE2-1,qAR,KB2LUV-1:!42=6.73NS07601.65W#PHG6800
20260223101211KD2AYD-3>APN383,KB2LUV-1*,WIDE2-1,qAR,WN8Z-4:!4256.73NS07601.>5W#PHG6800
20260223111453KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS0?601.65W#PHG6800
20260223114246KD2AYD-3>APN383,qAR,KB2LUV-1:!4256.73NS07601>65W#PHG6800 W2 Wilderness SAR Team