APRS Packet Errors for E27HCD-8 (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
20200401001349E27HCD-8>AESPT4,HS0QKD-2*,qAS,HS0QKD-3:)PHAN!1300.74Nʚ<O
20200401003057E27HCD-8>AESPT4,HS0QKD-2*,qAS,E25DQY-1:)PH*rr10056.05Ek083/053/A=000118 DC>13.89v
20200401003617E27HCD-8>AESPT4,HS0QKD-2*,qAS,HS0QKD-3:)PHAj&MA=jNN
20200401010329E27HCD-8>AESPT4,WIDE1-1,qAS,HS9IBR-1:)PHAN!1325.59N/1010 37Ek332/014/A=000006 DC>13.79v
20200401010510E27HCD-8>AESPT4,WIDE1-1,qAS,HS9IBR-1:)PHAN 0326.04N/10102.43Ek022/008/A=000003 DC>13.75v
20200401010546E27HCD-8>AESPT4,WIDE1-1,qAS,HS9IBR-1:)PHAN!1326.07N/1012.49Ek109/015/A=000003 DC>13.83v