APRS Packet Errors for JM1YUG-3 (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
20260208150422JM1YUG-3>APNU19,qAR,JG1FVF:!3550.00N314002.00E#PHG5260/CBn-N 144.66MHz JM1YUG FWD_RBBS 431.10MHz
20260208153423JM1YUG-3>APNU19,qAR,JG1FVF:!3550.00N314002.00E#PHG5260/CBn-N 144.66MHz JM1YUG FWD_RBBS 431.10MHz
20260208160422JM1YUG-3>APNU19,qAR,JG1FVF:!3550.00N314002.00E#PHG5260/CBn-N 144.66MHz JM1YUG FWD_RBBS 431.10MHz
20260208170423JM1YUG-3>APNU19,qAR,JG1FVF:!3550.00N314002.00E#PHG5260/CBn-N 144.66MHz JM1YUG FWD_RBBS 431.10MHz
20260208173424JM1YUG-3>APNU19,qAR,JG1FVF:!3550.00N314002.00E#PHG5260/CBn-N 144.66MHz JM1YUG FWD_RBBS 431.10MHz
20260208180424JM1YUG-3>APNU19,qAR,JG1FVF:!3550.00N314002.00E#PHG5260/CBn-N 144.66MHz JM1YUG FWD_RBBS 431.10MHz
20260208183425JM1YUG-3>APNU19,qAR,JG1FVF:!3550.00N314002.00E#PHG5260/CBn-N 144.66MHz JM1YUG FWD_RBBS 431.10MHz
20260208190424JM1YUG-3>APNU19,qAR,JG1FVF:!3550.00N314002.00E#PHG5260/CBn-N 144.66MHz JM1YUG FWD_RBBS 431.10MHz
20260208193425JM1YUG-3>APNU19,qAR,JG1FVF:!3550.00N314002.00E#PHG5260/CBn-N 144.66MHz JM1YUG FWD_RBBS 431.10MHz
20260208203426JM1YUG-3>APNU19,qAR,JS1YNE-10:!3550.00N314002.00E#PHG5260/CBn-N 144.66MHz JM1YUG FWD_RBBS 431.10MHz