APRS Packet Errors for HOPEMT (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
20260209085632HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAO,KO6KL-1:!3840.70N/12032.35W# 12.2V N6YBH
20260209092632HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAR,K6MRP-10:!3840.70N/12032.35W# 12.3V N6YBH
20260209092706HOPEMT>APOT30,KE6CAC,K6FGA-1*,WIDE2,qAR,W6PW-10:!3840.70N/12032.35W# 12.3V N6YBH
20260209095634HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAR,GTOWN:!3840.70N/12032.35W# 12.2V N6YBH
20260209102634HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAR,K6MRP-10:!3840.70N/12032.35W# 12.2V N6YBH
20260209105634HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAR,K6MRP-10:!3840.70N/12032.35W# 12.2V N6YBH
20260209112635HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAR,K6MRP-10:!3840.70N/12032.35W# 12.2V N6YBH
20260209115635HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAR,K6MRP-10:!3840.70N/12032.35W# 12.2V N6YBH
20260209122636HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAR,K6MRP-10:!3840.70N/12032.35W# 12.2V N6YBH
20260209125636HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAR,K6MRP-10:!3840.70N/12032.35W# 12.2V N6YBH
20260209132638HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAR,K6MRP-10:!3840.70N/12032.35W# 12.2V N6YBH
20260209135638HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAR,K6MRP-10:!3840.70N/12032.35W# 12.2V N6YBH
20260209142639HOPEMT>APOT30,WIDE1-1,WIDE2-1,qAO,FRNKLN:!3840.70N/12032.35W# 12.2V N6YBH