APRS Packet Errors for W8RMN-10 (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
20260208133018W8RMN-10>APWW11,APRS,WIDE1-1,WIDE2-2,qAR,HAMLTN:@133017h4226.64N/08540.01W#PHG5/30 APRS-IS for Win32
20260208140019W8RMN-10>APWW11,APRS,WIDE1-1,WIDE2-2,qAR,AC8HZ:@140017h4226.64N/08540.01W#PHG5/30 APRS-IS for Win32
20260208153022W8RMN-10>APWW11,APRS,WIDE1-1,WIDE2-2,qAR,KC8SWY-15:@153020h4226.64N/08540.01W#PHG5/30 APRS-IS for Win32
20260208160023W8RMN-10>APWW11,APRS,WIDE1-1,WIDE2-2,qAR,HAMLTN:@160021h4226.64N/08540.01W#PHG5/30 APRS-IS for Win32
20260208163024W8RMN-10>APWW11,APRS,WIDE1-1,WIDE2-2,qAR,HAMLTN:@163022h4226.64N/08540.01W#PHG5/30 APRS-IS for Win32
20260208170025W8RMN-10>APWW11,APRS,WIDE1-1,WIDE2-2,qAR,HAMLTN:@170023h4226.64N/08540.01W#PHG5/30 APRS-IS for Win32
20260208173026W8RMN-10>APWW11,APRS,WIDE1-1,WIDE2-2,qAR,HAMLTN:@173024h4226.64N/08540.01W#PHG5/30 APRS-IS for Win32
20260208180026W8RMN-10>APWW11,APRS,WIDE1-1,WIDE2-2,qAR,HAMLTN:@180025h4226.64N/08540.01W#PHG5/30 APRS-IS for Win32
20260208183027W8RMN-10>APWW11,APRS,WIDE1-1,WIDE2-2,qAR,AC8HZ:@183026h4226.64N/08540.01W#PHG5/30 APRS-IS for Win32
20260208190028W8RMN-10>APWW11,APRS,WIDE1-1,WIDE2-2,qAR,HAMLTN:@190027h4226.64N/08540.01W#PHG5/30 APRS-IS for Win32