APRS Packet Errors for OH2NJR (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
20260220062256OH2NJR>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@200622z6010.34N/02451.57E_29/001g003t004r000p000P000h87b10148 RX Igate & WX station
20260220063922OH2NJR>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@200639z6010.34N2451.57E_317/002g004t004r000p000P000h88b10149 RX Igate & WX station
20260220082806OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@200827z6010.34N/02451.57E_3/002g004t011r000p000P000h72b10158 RX Igate & WX station
20260220084627OH2NJR>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@200846z6010.34N/02451.57E_314/02g004t011r000p000P000h69b10158 RX Igate & WX station