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
20260208131652	VA5TM-13>APRS,TCPIP,qAC,T2TEXAS:;IRLP1800 081300z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300
20260208141653	VA5TM-13>APRS,TCPIP,qAC,T2OREGON:;IRLP1800 081400z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300
20260208151652	VA5TM-13>APRS,TCPIP,qAC,T2PR:;IRLP1800 081500z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300
20260208161652	VA5TM-13>APRS,TCPIP,qAC,T2TEXAS:;IRLP1800 081600z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300
20260208171652	VA5TM-13>APRS,TCPIP,qAC,T2CAEAST:;IRLP1800 081700z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300
20260208181652	VA5TM-13>APRS,TCPIP,qAC,T2CAEAST:;IRLP1800 081800z5023.69NL10531.99W&146.490MHz : LINKED TO REF9300