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
20250823041913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w3d23:35:48
20250823043913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w3d23:55:48
20250823044913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d00:05:48
20250823045913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d00:15:48
20250823050914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d00:25:48
20250823051913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d00:35:48
20250823052913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d00:45:48
20250823053913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d00:55:48
20250823054914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d01:05:48
20250823060913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d01:25:48
20250823062913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d01:45:48
20250823063913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d01:55:48
20250823070913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d02:25:48
20250823073913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d02:55:48
20250823074913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d03:05:48
20250823081913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d03:35:48
20250823082913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d03:45:48
20250823083913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d03:55:48
20250823084913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d04:05:48
20250823085913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d04:15:48
20250823090913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d04:25:48
20250823093913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d04:55:48
20250823095913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 37w4d05:15:48