APRS Packet Errors for E27ASY-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
20250912002835E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!1447.12N/100rE>306/0z000098
20250912003512E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!Lӓ)r10038.7LQzz000157Indy Tracker top speed 96 kmKDx 101 km.
20250912003534E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!1447.90NP10038.71/001/A=JTracker Dx:101 km
20250912003636E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!1447.87NP10¹71E>174 A=000108Indy Tracker Dx:101 km
20250912004022E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!1447.79N/Lr*270/0LM)000078
20250912004509E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!1447.74NP10037LNQ77/001/A=000095Indy Tracke."104 km
20250912004806E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!1447.99NP100)*303/000/A=000098Indy Tracker Dkm
20250912010830E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!1447.98NP100)*320/000)000131Ind^ɅɁDx:10Z
20250912012831E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!1448.00NP10037)182/000/A=000183Indy Tracker Dx:104 km
20250912014410E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!1447.99NP10)*095/000/A=000108Indy Tracker Dx:104 km
20250912020415E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!Lӓ)rA0037.19E>285/000/A=000137Indy TrackY."104 km
20250912023422E27ASY-8>AESPT4,WIDE1-1,qAR,HS1AL-1:!1447.99r*280/000/A=000150Indy Tracker Dx:104 km