APRS Packet Errors for OE2WNL-20 (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
20260209131810	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392
20260209134823	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392
20260209141839	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392
20260209144854	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392
20260209151909	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392
20260209154922	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392
20260209161937	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392
20260209164952	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392
20260209172007	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392
20260209175021	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392
20260209182036	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392
20260209185051	OE2WNL-20>APRSGW,TCPIP*,qAR,OE2WNL-20:!4726.03N/01250.09E-/B=100/A=002392