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
20260704024535OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@0402456010.34N/02451.57E_045/001g002t057r000p001P000h00b10035 RX Igate & WX station
20260704035421OH2NJR>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@040354z6010.34N/02451.57E_0001g002t057r000p001P000h00b10034 RX Igte & WX station
20260704072432OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@040724z6010.34N/02451027/000g001t062r000p001P000h82b10035 RX Igate & WX station
20260704074336OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@040743z6010.34N/02451.57E_183002g003t064r000p001P000h80b10034 RX Igate & WX station