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
20251015101151HS5NMF>AESPG4,WIDE1-1,qAR,E27ASY-2:@151010z1447.r10113.77EriGate by E28AM HS0AC T=32° H=59% P=975
20251015122628HS5NMF>AESPG4,WIDE1-1,qAR,E20TWR-1:@151225z1447.28N/10113.77E_000:00t085r...p...P...h63b09770L000 iGate by E28AM HS0AC T=29° H=63% P=977
20251015123713HS5NMF>AESPG4,WIDE1-1,qAR,HS5SQI-2:@1ML447.28N/10113.77E_000/000g000t085r...p...P...h64b09780L000 iGate by E28AM HS0AC T=29° H=64% P=978
20251015130933HS5NMF>AESPG4,WIDE1-1,qAR,HS1AH-10:@151308rꦊ* *ɓLN0Jѕby E28AM HS0AC T=28° H=66% P=978
20251015132028HS5NMF>AESPG4,WIDE1-1,qAR,E27ASY-2:@151318z1447.28N/101&*ɥѕby E28AM HS0AC T=29° H=62% P=978
20251015140324HS5NMF>AESPG4,WIDE1-1,qAR,HS1AL-1:@151401z14Ir10113.77E_000/000g000t085r...p...P...h64b09780L000 iGate by E28AM HS0AC T=29° H=64% P=978
20251015151328HS5NMF>AESPG4,WIDE1-1,qAR,E20ZNR-1:@151512z1447.28N/10LL&*}00/000g000t083r...p...P...h66b09790L000 iGate by E28AM HS0AC T=28° H=66% P=979