APRS Packet Errors for WB4YDL-2 (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
20260209090335	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260209093336	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260209100338	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260209103339	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260209110340	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260209113341	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260209120343	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260209123344	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260209130345	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260209133346	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260209140347	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi
20260209143348	WB4YDL-2>APIN21,TCPIP*,qAC,T2TEXAS:!3627.85N/08911.30W-Reelfoot Lake area Igate and digi