APRS Packet Errors for XE2OK-1 (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
20260208195540	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208201040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208202540	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208204040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208205540	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208211040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208212540	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208214040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208215540	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208221040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208222541	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208224040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208225540	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208231040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208232540	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208234040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208235540	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260208235543	XE2OK-1>APDW18,XE2SK-1*,WIDE2-1,qAS,XE2W-1:!2540.29NT10016.87W#PHG7170XE2OK DIGI Monterrey, N.L.
20260209001040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260209002540	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260209002543	XE2OK-1>APDW18,XE2SK-1*,WIDE2-1,qAS,XE2W-1:!2540.29NT10016.87W#PHG7170XE2OK DIGI Monterrey, N.L.
20260209004040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260209004043	XE2OK-1>APDW18,XE2SK-1*,WIDE2-1,qAS,XE2W-1:!2540.29NT10016.87W#PHG7170XE2OK DIGI Monterrey, N.L.
20260209005540	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260209005543	XE2OK-1>APDW18,XE2SK-1*,WIDE2-1,qAS,XE2W-1:!2540.29NT10016.87W#PHG7170XE2OK DIGI Monterrey, N.L.
20260209011040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260209011043	XE2OK-1>APDW18,XE2SK-1*,WIDE2-1,qAS,XE2W-1:!2540.29NT10016.87W#PHG7170XE2OK DIGI Monterrey, N.L.
20260209012540	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260209012543	XE2OK-1>APDW18,XE2SK-1*,WIDE2-1,qAS,XE2W-1:!2540.29NT10016.87W#PHG7170XE2OK DIGI Monterrey, N.L.
20260209014040	XE2OK-1>APDW18,TCPIP*,qAC,APRSMX-1:!2540.29NT10016.87W#PHG7170Monterrey, Nuevo León
20260209014043	XE2OK-1>APDW18,XE2SK-1*,WIDE2-1,qAS,XE2W-1:!2540.29NT10016.87W#PHG7170XE2OK DIGI Monterrey, N.L.