APRS Packet Errors for OH2MUI (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
20260917034958OH2MUI>APRX29,OH2RDU,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@170349z6024.43N/0235.73E_000/000g000t056r001p044P007h97b09989 RX Igate & WX station
20260917042705OH2MUI>APRX29,OH2RCH-2,WIDE2*,qAR,OH7JHF-1:@10426z6024.43N/02352.73E_000/000g000t055r001p044P008h98b09991 RX Igate & WX station
20260917054000OH2MUI>APRX29,OH2RCH-2,WIDE2*,qAR,OH7JHF-1:@170539z60243N/02352.73E_273/001g001t055r001p044P009h96b09989 RX Igate & WX station
20260917085051OH2MUI>APRX29,OH2RCH-2,WIDE2*,qAR,OH7JHF-1:@17850z6024.43N/02352.73E_000/000g001t056r001p044P014h97b09994 RX Igate & WX station