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
20251208084000E27ASY-2>AESPG4,qAR,E20ZNR-1:@080839z1445.26N/10043NNQKRIgate T=35° H=31% P=1009
20251208084515E27ASY-2>AESPG4,qAR,HS1AL-1:@0¢445.26N/10043.99E_000/0:00t095r...p...P...h31b10090LJIgate T=35° H=31% 1009
20251208090141E27ASY-2>AESPG4,qAR,HS1AL-1:@08ʂz1445.2)r*Indy Igate T=35°% P=1009
20251208110120E27ASY-2>AESPG4,qAR,HS1AL-1:@081101z1445.26N/Lr*Ind^JѕT=34° H=33% P=1010
20251208121720E27ASY-2>AESPG4,qAR,HS1AL-1:@081217z144MIr10043.99E_000/000g000t094r...p...P...h33b101b00 Indy VѕT=34° H=33% P=1011
20251208140053E27ASY-2>AESPG4,qAR,HS1AL-1:@081400z14SIr10043.99E-Indy Igate T=& H=34% P=L
20251208140618E27ASY-2>AESPG4,qAR,HS1AL-1:@081405z1445.26N/10043.9QKRIgate T=34° H=33% P=10L&