APRS Packet Errors for R3KEE-1 (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
20260819042913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w1d23:11:18
20260819043914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w1d23:21:18
20260819044914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w1d23:31:18
20260819045913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w1d23:41:18
20260819050914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w1d23:51:18
20260819051914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d00:01:18
20260819052915	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d00:11:18
20260819053914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d00:21:18
20260819054914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d00:31:18
20260819055913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d00:41:18
20260819061914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d01:01:18
20260819062914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d01:11:18
20260819063913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d01:21:18
20260819064914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d01:31:18
20260819065914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d01:41:18
20260819070913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d01:51:18
20260819071914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d02:01:18
20260819072914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d02:11:18
20260819073914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d02:21:18
20260819074913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d02:31:18
20260819075915	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d02:41:18
20260819080913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d02:51:18
20260819081913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d03:01:18
20260819082913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d03:11:18
20260819083914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d03:21:18
20260819084914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d03:31:18
20260819085913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d03:41:18
20260819090915	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d03:51:18
20260819091914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d04:01:18
20260819092913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d04:11:18
20260819093914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d04:21:18
20260819094913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d04:31:18
20260819095914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d04:41:18
20260819100914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d04:51:18
20260819101914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 24w2d05:01:18