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
20260726075133OH2MUI>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@260751z6024.43N/02352.7E_000/000g000t061r000p002P002h91b10004 RX Igate & WX station
20260726083037OH2MUI>APRX29,WIDE2-1,qAR,OH7JHF-1:@260830z6024.43N/0252.73E_250/002g002t062r000p002P02h89b10007 RX Igate & WX station
20260726084736OH2MUI>APRX29,WIDE2-1,qAR,OH7JHF-1:@260847z6024.4N/02352.73E_180/002g002t061r000p002P002h87b10006 RX Igate & WX station
20260726092724OH2MUI>APRX29,WIDE2-1,qAR,OH7JHF-1:@260927z643N/02352.73E_000/000g003t061r001p003P003h90b10007 RX Igate & WX station