APRS Packet Errors for ON4ALV (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
20260209103019	ON4ALV>APRS,TCPIP,qAC,T2BC:!5048.57N/00510.70E[Unified Radios on RFinder-M6*
20260209110518	ON4ALV>APRS,TCPIP,qAC,T2USANW:!5048.57N/00510.70E[Unified Radios on RFinder-M6*
20260209111018	ON4ALV>APRS,TCPIP,qAC,T2MCI:!5048.57N/00510.70E[Unified Radios on RFinder-M6*
20260209112018	ON4ALV>APRS,TCPIP,qAC,T2TEXAS:!5048.57N/00510.70E[Unified Radios on RFinder-M6*
20260209160029	ON4ALV>APRS,TCPIP,qAC,T2MCI:!5048.57N/00510.70E[Unified Radios on RFinder-M6*
20260209162027	ON4ALV>APRS,TCPIP,qAC,T2NALA:!5048.57N/00510.70E[Unified Radios on RFinder-M6*