APRS Packet Errors for E27CYF-1 (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
20250223205517E27CYF-1>AESPG4,qAR,HS1AL-1:@232055z1445.25)r*}00/000g000t096r... rrB5b10100L000 Indy Igate T=35° H=35% P=L
20250223211544E27CYF-1>AESPG4,qAR,HS1AL-1:@232115z1445.25N/100r8E;IndyRVѕ T=35° H=35% P=1011
20250223221708E27CYF-1>AESPG4,qAR,HS1AL-1:@232217z1445.25N/100&)*Indy IgXW35° H=36% P=1011
20250223223735E27CYF-1>AESPG4,qAR,HS1AL-1:@232237z1445.25N/10r8E;IndyRVѕ T=35° H=36% P=1011
20250223225804E27CYF-1>AESPG4,qAR,E20ZNR-1:@232258z144Ir10043.98E;Indy Igate T=35° H=36% P=1012
20250224022256E27CYF-1>AESPG4,qAR,HS1AL-1:@240222z1445.25N)r*Indy Igate T=35° H=36% P=1015