APRS Packet Errors for JF6YNZ-2 (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
20260208132554JF6YNZ-2>APRS,qAR,JG6YPO-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps
20260208135555JF6YNZ-2>APRS,qAR,JG6YPO-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps
20260208142555JF6YNZ-2>APRS,qAS,JE6DXS-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps
20260208145555JF6YNZ-2>APRS,qAS,JE6DXS-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps
20260208152555JF6YNZ-2>APRS,qAS,JE6DXS-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps
20260208155555JF6YNZ-2>APRS,qAR,JG6YPO-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps
20260208162555JF6YNZ-2>APRS,qAR,JG6YPO-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps
20260208165555JF6YNZ-2>APRS,qAS,JE6DXS-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps
20260208172555JF6YNZ-2>APRS,qAS,JE6DXS-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps
20260208175555JF6YNZ-2>APRS,qAS,JE6DXS-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps
20260208182555JF6YNZ-2>APRS,qAS,JE6DXS-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps
20260208185556JF6YNZ-2>APRS,qAS,JE6DXS-10:!3118.54NS13049.48E#PHG76502/W1 Mt.Yokoo 144.64Mhz 9.6bps