APRS Packet Errors for VE6AQ-1 (last 24 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
20250711170458VE6AQ-1>APOT03,EDMNTN,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711170731VE6AQ-1>APOT03,EDMNTN,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711170822VE6AQ-1>APOT03,EDMNTN,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711170913VE6AQ-1>APOT03,EDMNTN,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711171005VE6AQ-1>APOT03,EDMNTN,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711171056VE6AQ-1>APOT03,VE6GPS,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711171147VE6AQ-1>APOT03,EDMNTN,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711171420VE6AQ-1>APOT03,EDMNTN,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711171602VE6AQ-1>APOT03,EDMNTN,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711171653VE6AQ-1>APOT03,EDMNTN,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711171744VE6AQ-1>APOT03,EDMNTN,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711171926VE6AQ-1>APOT03,EDMNTN,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711172019VE6AQ-1>APOT03,EDMNTN,WIDE1,WINFLD,WIDE2*,qAR,VE6XVK-1:!0000.00N/00000.00E
20250711172109VE6AQ-1>APOT03,VE6GPS,WIDE1*,WIDE2-1,qAR,VE6XVK-1:!0000.00N/00000.00E