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
20250418055916	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d01:16:27
20250418060914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d01:26:27
20250418061914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d01:36:27
20250418062914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d01:46:27
20250418063914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d01:56:27
20250418064914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d02:06:27
20250418065914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d02:16:27
20250418070914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d02:26:27
20250418071914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d02:36:27
20250418072914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d02:46:27
20250418073914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d02:56:27
20250418074914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d03:06:27
20250418075914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d03:16:27
20250418080914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d03:26:27
20250418081914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d03:36:27
20250418082915	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d03:46:27
20250418083916	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d03:56:27
20250418084914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d04:06:27
20250418085914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d04:16:27
20250418090914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d04:26:27
20250418091914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d04:36:27
20250418092914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d04:46:27
20250418093914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d04:56:27
20250418094915	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d05:06:27
20250418095914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d05:16:27
20250418100914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d05:26:27
20250418101914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d05:36:27
20250418102914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d05:46:27
20250418103915	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d05:56:27
20250418104914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d06:06:27
20250418105914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d06:16:27
20250418110914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d06:26:27
20250418111914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d06:36:27
20250418112914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d06:46:27
20250418113914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d06:56:27
20250418114914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 19w3d07:06:27