APRS Packet Errors for DB0MOE (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
20260208131232DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM
20260208134231DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM
20260208141233DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM
20260208144231DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM
20260208151231DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM
20260208154233DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM
20260208161232DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM
20260208164231DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM
20260208171232DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM
20260208174231DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM
20260208181233DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM
20260208184231DB0MOE>APU25N,TCPIP*,qAC,T2PRT:=4835.81N/00804.43Em# C4FM # 144,865 MHZ # 145.500Mhz FM