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
20250313121202E27CYF-1>AESPG4,qAR,HS1AL-1:@131212z1445.25N/10043.9E_000/000g000t101r...p...P...h34b10060L000 Indy Igate T=38° H=34% P=1006
20250313145600E27CYF-1>AESPG4,qAR,HS1AL-1:@131456z1445.25N/10043.N*íIndy Igate T=37° H=36% P=1009
20250313155717E27CYF-1>AESPG4,qAR,HS1AL-1:@131557z1445.25N/L‚¢šrÊÂ*}Á00/000g000t100r...p...P...h37b10100L000 Indy Igate T=37° H=37% P=1010
20250313161743E27CYF-1>AESPG4,qAR,HS1AL-1:@131617z1445.25N/1˜¢šrÊÂ*}Á00/000g000t100r...p...P...h37b10090L000 Indy Igate T=37° H=37% P=1009