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
20261109124941OH2MUI>APRX29,OH2RCH-2,WIDE2*,qAR,OH7JHF-1:@01249z6024.43N/02352.73E_242/003g004t039r000p021P014h87b10195 RX Igate & WX station
20261109130737OH2MUI>APRX29,WIDE2-1,qAR,OH7JHF-1:@09130z6024.43N/02352.73E_238/004g004t039r000p021P014h87b10194 RX Igate & WX station
20261109144721OH2MUI>APRX29,OH2RCH-2,WIDE2*,qAR,OH7JHF-1:@0914476024.43N/02352.73E_245/006g007t038r000p021P014h89b10189 RX Igate & WX station