APRS Packet Errors for XE3RFM (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
20260209103721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz
20260209110721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz
20260209113721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz
20260209120721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz
20260209123721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz
20260209130721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz
20260209133721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz
20260209140721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz
20260209143721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz
20260209150721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz
20260209153721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz
20260209160721	XE3RFM>APDW17,TCPIP*,qAC,T2TEXAS:!2109.91N/09001.45WyIGATE SISAL YUC. 144.390 MHz