APRS Packet Errors for YO7HYD-3 (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
20260208151630	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS
20260208154630	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS
20260208161632	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS
20260208164630	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS
20260208171630	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS
20260208174630	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS
20260208181630	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS
20260208184630	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS
20260208191630	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS
20260208194630	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS
20260208201630	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS
20260208204630	YO7HYD-3>APGWM9,TCPIP*,qAC,SECOND:=4516.63N/02503.36E`GPRS/GSM conversion to APRS