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
20250420150052E27CYF-1>AESPG4,qAR,HS1AL-1:@201500z1445.25N)‚‚¢šrÊÂ*íIndy Igate T=37° H=31% P=1007
20250420154148E27CYF-1>AESPG4,qAR,E20ZNR-1:@201541z1445.25N/L‚¢šrÊÂ*íIndy Igate T=36° H=33% P=1007
20250420162234E27CYF-1>AESPG4,qAR,HS1AL-1:@201“’ÒÅ445.25N/10043.98E_000/00:Á00t100r—É ¹..P...h&&¬‚‚º‚bÁ00 Indy Igate T=37° H=32% P=1007
20250420170331E27CYF-1>AESPG4,qAR,HS1AL-1:@201703z1445.25N/10043.98E_00 ‚‚:Á00t10.ÉÉ ¹..P...h32b10070L000 Indy Igate T=37° H=32% P=1007
20250420172400E27CYF-1>AESPG4,qAR,HS1AL-1:@201724z1445.25N/10043.N*}Á00/000g000t100r...p...P...h33b10070L000 Indy Igate T=37° H=33% P=1007