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
20260518045527	OH2MUI>APRX29,WIDE2-1,qAR,OH7JHF-1:@18046024.43N/02352.73E_000/000g001t040r000p000P000h99b10218 RX Igate & WX station
20260518053103	OH2MUI>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@180530024.43N/02352.73E_000/000g000t043r000p000P000h99b10219 RX Igate & WX station
20260518095827	OH2MUI>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@180958z60202352.73E_334/002g002t062r000p000P000h41b10217 RX Igate & WX station