APRS Packet Errors for IRLP1376 (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
20260209130001	VE5FXR-13>APRS,TCPIP,qAC,T2OREGON:;IRLP1376 091300z5245.12NL10403.40W&146.700MHz- : LINKED TO REF9300
20260209140001	VE5FXR-13>APRS,TCPIP,qAC,T2BC:;IRLP1376 091400z5245.12NL10403.40W&146.700MHz- : LINKED TO REF9300
20260209150001	VE5FXR-13>APRS,TCPIP,qAC,T2OREGON:;IRLP1376 091500z5245.12NL10403.40W&146.700MHz- : LINKED TO REF9300
20260209160001	VE5FXR-13>APRS,TCPIP,qAC,T2DALLAS:;IRLP1376 091600z5245.12NL10403.40W&146.700MHz- : LINKED TO REF9300
20260209170001	VE5FXR-13>APRS,TCPIP,qAC,T2TEXAS:;IRLP1376 091700z5245.12NL10403.40W&146.700MHz- : LINKED TO REF9300
20260209180001	VE5FXR-13>APRS,TCPIP,qAC,T2USANE:;IRLP1376 091800z5245.12NL10403.40W&146.700MHz- : LINKED TO REF9300