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
20260819050702	OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@19006z6010.34N/02451.57E_065/002g004t055r000p000P000h87b09994 RX Igate & WX station
20260819090026	OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@190859z6010.34N/02451.57E_32/002g006t064r000p000P0h62b09 RXIgate & WX station
20260819091716	OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@190916z6010.34N/02451.57E_3002g006t066r000p000P000h53988 RX Igate & WX station