APRS Packet Errors for UR5MHI-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
20260209094501UR5MHI-L>APRS,TCPIP*,qAO,UR5MHI:=4820.57N/03950.10ErEcholink 145.600 MHz #77 H=35m P=50W
20260209101501UR5MHI-L>APRS,TCPIP*,qAO,UR5MHI:=4820.57N/03950.10ErEcholink 145.600 MHz #77 H=35m P=50W
20260209104501UR5MHI-L>APRS,TCPIP*,qAO,UR5MHI:=4820.57N/03950.10ErEcholink 145.600 MHz #77 H=35m P=50W
20260209111501UR5MHI-L>APRS,TCPIP*,qAO,UR5MHI:=4820.57N/03950.10ErEcholink 145.600 MHz #77 H=35m P=50W
20260209121501UR5MHI-L>APRS,TCPIP*,qAO,UR5MHI:=4820.57N/03950.10ErEcholink 145.600 MHz #77 H=35m P=50W
20260209124501UR5MHI-L>APRS,TCPIP*,qAO,UR5MHI:=4820.57N/03950.10ErEcholink 145.600 MHz #77 H=35m P=50W
20260209131501UR5MHI-L>APRS,TCPIP*,qAO,UR5MHI:=4820.57N/03950.10ErEcholink 145.600 MHz #77 H=35m P=50W
20260209134501UR5MHI-L>APRS,TCPIP*,qAO,UR5MHI:=4820.57N/03950.10ErEcholink 145.600 MHz #77 H=35m P=50W
20260209141501UR5MHI-L>APRS,TCPIP*,qAO,UR5MHI:=4820.57N/03950.10ErEcholink 145.600 MHz #77 H=35m P=50W
20260209144501UR5MHI-L>APRS,TCPIP*,qAO,UR5MHI:=4820.57N/03950.10ErEcholink 145.600 MHz #77 H=35m P=50W
20260209151501UR5MHI-L>APRS,TCPIP*,qAO,UR5MHI:=4820.57N/03950.10ErEcholink 145.600 MHz #77 H=35m P=50W