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
20260816022149OH2NJR>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@60221z6010.34N/02451.57E_100/002g004t062r000p002P002h91b10041 RX Igate & WX station
20260816033101OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@160330z6010.3/02451.57E_087/001g003t062r000p002P002h90b10037 RX Igate & WX station
20260816055736OH2NJR>APRX29,WIDE2-1,qAR,OH7JHF-1:@160557z60.34N/02451.57E_171/002g005t064r000p002P002h82b10017 RX Igate & WX station
20260816063608OH2NJR>APRX29,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:@160635z6010.34N/02451.57_190/003g006t065r000p002P002h80b10013 RX Igate & WX station