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
20260814214506HS5NMF>AESPG4,WIDE1-1,qAR,E20ZNR-1:@1421z1447.28N/10113.77EriGate by E28AM HS0AC T=28° H=99% P=975
20260814224417HS5NMF>AESPG4,WIDE1-1,qAR,HS2AC-1:@1&&447.28N/10113.77E_000/000g000t083r...p...P...h99b09750L000 iGate by E28AM HS0AC T=28° H=99% P=975
20260814233313HS5NMF>AESPG4,HS1AH-10*,qAR,HS6AU:@14248N1*ɥѕ%TRAC2 9A
20260814235439HS5NMF>AESPG4,HS1AH-10*,qAR,E22LPB:@142354z1447.28N/10113.77Qѕby E28AM HS0AC T=28° H=99% P=976
20260815011027HS5NMF>AESPG4,HS1AH-10*,qAR,E20TWR-1:@150110z1447.2r10113.77EriGate by E28AM HS0AC T=29° H=97% P=977
20260815013154HS5NMF>AESPG4,WIDE1-1,qAR,HS0TK-1:@150131z1447.28N/10113.Sz:00t086r...p...P...h97b09770L000 iGate by E28AM HS0AC T=29° H=97% P=977
20260815022035HS5NMF>AESPG4,WIDE1-1,qAR,E27ASY-2:@150220z1447.28N/10113.77E_000/:00t087r...p...P...h93b09770L000 iGate by E28AM HS0AC T=30° H=93% P=977