APRS Packet Errors for HB9FEE-40 (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
20260208200319HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352
20260208203334HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352
20260208210345HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352
20260208213400HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352
20260208220415HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352
20260208223432HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352
20260208230447HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352
20260208233502HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352
20260209000517HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352
20260209003536HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352
20260209010550HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352
20260209013606HB9FEE-40>APRSGW,TCPIP*,qAR,HB9FEE-40:!4710.62N/00825.29E&MeshCom iGate/B=100/A=001352