APRS Packet Errors for KP4SC-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
20251008215921KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251008220921KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251008221922KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251008222921KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251008223921KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251008224922KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251008225921KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251008230921KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251008231922KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251008232921KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251008233921KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251009024922KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W
20251009025921KP4SC-3>APN382,WIDE2-1,qAO,KP4SC-2:!1824.22NS06704.13W