APRS Packet Errors for HS5NMF (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
20261020215215HS5NMF>AESPG4,WIDE1-1,qAR,HS1AL-1:@202151z1447.28)r*ɥѕby E28AM HS0AC T=26° H=99% P=980
20261020220257HS5NMF>AESPG4,WIDE1-1,qAR,E27ASY-2:@202202z1447.28N/Lr*}00/000g000t081r...p...P...h99b09800L000 iGate by E28AM HS0AC T=27° H=99% P=980
20261020220306HS5NMF>AESPG4,WIDE1-1,qAR,E20ZNR-1:@447.28N/10113.77EriGate by E28AM HS0AC T=27° H=99% P=980
20261020225133HS5NMF>AESPG4,WIDE1-1,qAR,HS1AL-1:@202250z1447.28N/10113.77E_000/0:00t080r...p...P...h99b09800L000 iGate by E28AM HS0AC T=26° H=99% P=980
20261020232408HS5NMF>AESPG4,HS1AH-10*,qAR,E20TWR-1:@errr*WQ&SS0N
20261020234018HS5NMF>AESPG4,WIDE1-1,qAR,HS1AL-1:@202339z1447.28N/10LL&*ɥѕby E28AM HS0AC T=28° H=99% P=981
20261021004007HS5NMF>AESPG4,WIDE1-1,qAR,HS3RXX-3:@210&ST,25Փ9
20261021004524HS5NMF>AESPG4,WIDE1-1,qAR,HS6GVH-1:@210044z1447.2)r*ɥѕby E28AM HS0AC T=30° H=99% P=982
20261021010138HS5NMF>AESPG4,WIDE1-1,qAR,HS3RXX-3:@210100z1447.28N/10ͺ*W/*j5DէON
20261021011229HS5NMF>AESPG4,WIDE1-1,qAR,E20ZNR-1:@210111z1447.28N/1r*ɥѕby E28AM HS0AC T=31° H=96% P=982
20261021012307HS5NMF>AESPG4,WIDE1-1,qAR,HS3RXX-3:@210122z1447.28N/10113.7}z:ʒrLiG*(31° H=96% P=982