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
20261019231445OH2NJR>APRX29,WIDE2-2,qAR,OH7JHF-1:@192314z6010.34/02451.57E_165/001g001t044r000p000P000h74b10395 RX Igate & WX station
20261020000342OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@200002z6010.34N/02451.5_68/001g002t043r000p000P000h77b10394 RX Igate & WX station
20261020013321OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@200132z6010.34NE_035/000g001t037r00p000P000h96b10388 RX Igate & WX station
20261020040042OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@200400z60134N/02451.57E_125/000g000t035r000p000P000h99b10384 RX Igate & WX station