APRS Packet Errors for E27ASY-2 (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
20251213024414E27ASY-2>AESPG4,qAR,E20TWR-1:@130243z144MI²r½10043.99E_000/000g000t092r...p...P...h46b10110L000 Indy Igate T=33° H=46% P=1011
20251213032739E27ASY-2>AESPG4,qAR,E22KKC-7:@130327½LS“I²r½10043.99E_000/000g000t093r...p...P...h46b10110L000 Indy Igate T=33° H=46% P=1011
20251213043256E27ASY-2>AESPG4,qAR,E22KKC-7:@130432z1445.26N)‚‚¢šrÊÊ*}Á00/000g000t094r...p...P...h44b10100L000 Indy Igate T=34° H=44% P=1010
20251213050809E27ASY-2>AESPG4,qAR,E20TWR-1:@130507z1445.26N/10043.99E_000/0˜:Á00t094r...p...P...h43b10100L000 Indy Igate T=34° H=43% P=1010
20251213053517E27ASY-2>AESPG4,qAR,E20TWR-1:@130534z1445.26N/10043—NNQ‚‚z‚‚‚:Á00t092r...p...P...h46b10090L000 Indy Igate T=33° H=46% P=1009