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
20251219164936E27ASY-2>AESPG4,qAR,HS1AL-1:@191649z1445.26N/10043.99E_000/0:00t093r...p...P...h37b1008 Indy Igate T=34° H=37% P=1008
20251219170039E27ASY-2>AESPG4,qAR,HS1AL-1:@191700z14SIr10043.NNQKRIgate T=34° H=37% P=1008
20251219170605E27ASY-2>AESPG4,qAR,HS1AL-1:@191705z1445.26N/100&)*Indy Igate T=34° H=37%Պ08
20251219171647E27ASY-2>AESPG4,qAR,HS1AL-1:@191716z1445.26N/10043.99E_00 :00t093r...p...P...h37b10080L000 Indy Igate T=34° H=37% P=1008
20251219190542E27ASY-2>AESPG4,qAR,HS1AL-1:@191905z1445.26N/10r*Indy Igate T=33° H=37% P=1007
20251219191106E27ASY-2>AESPG4,qAR,HS1AL-1:@191910z1445.r10043.99E-Indy Igate T=33° H=37% P=1007
20251219193251E27ASY-2>AESPG4,qAR,HS1AL-1:@191932z1445.26N/10043.99QKRIgate T=33° H=37% P=1007
20251219204837E27ASY-2>AESPG4,qAR,HS1AL-1:@192048z1445.26N/100&)*Indy Igate T=33° H=37% POL
20251219204907E27ASY-2>AESPG4,qAR,HS1AH-10:@192048zђ&&NQKdyST0
20251219213723E27ASY-2>AESPG4,qAR,HS1AL-1:@192136z14SIr10043.99E-Indy Igate T=33° H=38% P=1007
20251219222042E27ASY-2>AESPG4,qAR,HS1AL-1:@192220z1445.26N/L99E-Indy Igate T=33° H=38% P=1007