APRS Packet Errors for RO3M-L (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
20260209143102	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3
20260209150001	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3
20260209153102	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3
20260209160001	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3
20260209163101	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3
20260209170001	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3
20260209173101	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3
20260209180001	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3
20260209183102	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3
20260209190001	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3
20260209193102	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3
20260209200001	RO3M-L>APRSEL,RUS1-1,TCPIP*,qAU,T2TROITSK:=5735.67NE03951.68E0YAR FRN 145.350 MHz T127.3