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
20260318221333OH2MUI>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@182211z6024.42N/02352.74E_21/002g006t034r000p000P000h00b10253 RX igate and WX station
20260318230630OH2MUI>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@182301z6024.42N/0352.74E_212/002g005t035r000p000P000h00b10249 RX igate and WX station
20260319003839OH2MUI>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@190036z624.42N/02352.74E_209/001g003t035r000p000P000h00b10235 RX igate and WX station