APRS Packet Errors for VE6AAF (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
20240505080649VE6AAF>APN391,GIROUX,VE6OL-1*,WIDE2,qAR,VA6JN:!5608.76nN11744.55W#W2,ABn-N bERWYNbBerwyn VE6AAF
20240505080650VE6AAF>APN391,GIROUX,VE6OL-1*,WIDE2,qAR,VE6ARC-1:!5608.76n N11744.55W#W2,ABn-N bERWYN b Berwyn VE6AAF
20240505081649VE6AAF>APN391,GIROUX,VE6OL-1*,WIDE2,qAR,VA6JN:!5608.76nN11744.55W#W2,ABn-N bERWYNbBerwyn VE6AAF
20240505081650VE6AAF>APN391,GIROUX,VE6OL-1*,WIDE2,qAR,VE6ARC-1:!5608.76n N11744.55W#W2,ABn-N bERWYN b Berwyn VE6AAF
20240505095649VE6AAF>APN391,GIROUX,VE6OL-1*,WIDE2,qAR,VA6JN:!5608.76nN11744.55W#W2,ABn-N bERWYNbBerwyn VE6AAF
20240505095650VE6AAF>APN391,GIROUX,VE6OL-1*,WIDE2,qAR,VE6ARC-1:!5608.76n N11744.55W#W2,ABn-N bERWYN b Berwyn VE6AAF
20240505112650VE6AAF>APN391,GIROUX,VE6OL-1*,WIDE2,qAR,VA6JN:!5608.76nN11744.55W#W2,ABn-N bERWYNbBerwyn VE6AAF
20240505112650VE6AAF>APN391,GIROUX,VE6OL-1*,WIDE2,qAR,VE6ARC-1:!5608.76n N11744.55W#W2,ABn-N bERWYN b Berwyn VE6AAF
20240505134649VE6AAF>APN391,GIROUX*,WIDE2-1,qAR,VA6JN:!5608.76nN11744.55W#W2,ABn-N bERWYNbBerwyn VE6AAF
20240505134650VE6AAF>APN391,GIROUX,VE6OL-1*,WIDE2,qAR,VE6ARC-1:!5608.76n N11744.55W#W2,ABn-N bERWYN b Berwyn VE6AAF