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
20251112122725HS5NMF>AESPG4,WIDE1-1,qAR,E20ZNR-1:@121227z1447.28N/101&*}00/000g000t089r...p...P...h60b09780L000 iGate by E28AM HS0AC T=31° H=60% P=978
20251112125425HS5NMF>AESPG4,WIDE1-1,qAR,HS1AL-1:@121254z1447.28N/10113.77E_000/0088r...p...P...h61b09790L000 iGate by E28AM HS0AC T=31° H=61% P=979
20251112125435HS5NMF>AESPG4,WIDE1-1,qAR,E20TWR-1:@121254z1447.28N/1r*ɥѕby E28AM HS0AC T=31° H=61% P=979
20251112132135HS5NMF>AESPG4,WIDE1-1,qAR,HS1AH-10:@121321z1447.28N/1źJ55ԁTO9
20251112144818HS5NMF>AESPG4,WIDE1-1,qAR,HS1AH-10:@121447z1447.28N/10ͺ* . &N0L J*T=30° H=61% P=980
20251112164658HS5NMF>AESPG4,WIDE1-1,qAR,HS1AL-1:@121646z14Ir10113.77E_000/000g000t086r...p...P...h63b09800L000 iGate by E28AM HS0AC T=30° H=63% P=980
20251112175807HS5NMF>AESPG4,WIDE1-1,qAR,HS1AL-1:@121757z1447.28N/10113.77E_00 :00t084r...p...P...h66b09800L000 iGate by E28AM HS0AC T=28° H=66% P=980