APRS Packet Errors for HS1BJP (last 24 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
20250401155125HS1BJP>APRX20,qAR,HS2AC-1:!1422.48Nr*HSDXA Igate
20250401162918HS1BJP>APRX20,qAR,HS1AL-1:!1422r10029.18QKjEaIgate
20250401203004HS1BJP>APRX20,qAR,HS1AL-1:!142&r10029.18E-HSDXA Igate
20250401234357HS1BJP>APRX20,qAR,HS1AL-1:!1422.4r10029.18E-HSDXA Igate
20250402003537HS1BJP>APRX20,qAR,HS1AL-1:!1422.48N/10029.1QKjEaIgat
20250402014348HS1BJP>APRX20,qAR,HS1AL-1:!1422.48N/10029.1QKjEaIgate
20250402084510HS1BJP>APRX20,qAR,HS1AL-1:!1422.48N/Lr*HSDXA Igate
20250402125619HS1BJP>APRX20,qAR,HS1AL-1:!14&&r1002)*HSDXPJѕ
20250402134913HS1BJP>APRX20,qAR,HS0TK-1:!1422.48N/Lr*HSDXA Igate
20250402135355HS1BJP>APRX20,qAR,HS5TQA:!1422.48N/10029.fddjo