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
20260905054213HS5NMF>AESPG4,WIDE1-1,qAR,HS1AL-1:@050542z14Ir10113.77E_000/000g000t094r...p...P...h71b09780L000 iGate by E28AM HS0AC T=34° H=71% P=978
20260905062533HS5NMF>AESPG4,WIDE1-1,qAR,HS3RXX-3:@050625z1447.9r*%B&͂
20260905063056HS5NMF>AESPG4,WIDE1-1,qAR,HS3RXX-3:@050630z1447.2ST^&SPO°*
20260905064651HS5NMF>AESPG4,WIDE1-1,qAR,HS3RXX-3:@050646z1447.28N/10113.7}0 &N0LEBD՚ H=71% P=976
20260905091228HS5NMF>AESPG4,WIDE1-1,qAR,E20ZNR-1:@050912z1447.28N/10113.77E_000/0:00t096r...p...P...h66b09740L000 iGate by E28AM HS0AC T=35° H=66% P=974
20260905095541HS5NMF>AESPG4,HS1AH-10*,qAR,E20TWR-1:@050955z1447.28N/Lr*}00/000g000t096r...p...P...h63b09750L000 iGate by E28AM HS0AC T=35° H=63% P=975