APRS Packet Errors for IRLP1800 (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
20260209161650	VA5TM-13>APRS,TCPIP,qAC,T2BC:;IRLP1800 091600z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300
20260209171649	VA5TM-13>APRS,TCPIP,qAC,T2TEXAS:;IRLP1800 091700z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300
20260209181649	VA5TM-13>APRS,TCPIP,qAC,T2BC:;IRLP1800 091800z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300
20260209191649	VA5TM-13>APRS,TCPIP,qAC,T2CAWEST:;IRLP1800 091900z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300
20260209201649	VA5TM-13>APRS,TCPIP,qAC,T2CAWEST:;IRLP1800 092000z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300
20260209211649	VA5TM-13>APRS,TCPIP,qAC,T2MCI:;IRLP1800 092100z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300