Ikedor1
Offline 217.62.252.150:28015 checked 43d ago
Server instruments
no direct query in 48 hoursPlayers now
17% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 209/250
- 200/225
- 17/250
- 18/250
- 19/100
- 105/200
Quick answers
from the figures on this pageReset cycle
What wipe timing does Ikedor1 follow?
To tell the rhythm of Ikedor1, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 47 days 19 hours ago.
Tags
Which tags does Ikedor1 carry, and what do they mean?
Tags published by Ikedor1, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp6 (Max players): 6 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Ikedor1?
Rust Metrics lists featuring Ikedor1: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does Ikedor1 sit in the rankings?
Player hours over seven days put Ikedor1 at #13,258, in the top – of all ranked servers.
How full does Ikedor1 get?
Ikedor1 is not responding; status offline, last seen 43 days 14 hours ago.
Server
What location is Ikedor1 hosted in?
Reading: location. Ikedor1 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 217.62.252.150:28015.
What Rust version is Ikedor1 on?
Rust network protocol 2633 and build 163794 on Windows is the build Ikedor1 runs. To get in, your game needs the same protocol; Steam applies the update.
Is Ikedor1 up, and how often does it stay up?
Reading: offline. Ikedor1 last answered 43 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
How is Ikedor1 configured, and what rules are in force?
Check: gather rate. The name Ikedor1 does not state one. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
Which map is live on Ikedor1?
Procedural map on Ikedor1, made by the game's generator.
How to join
How do you connect to Ikedor1?
Press F1 in Rust and enter client.connect 217.62.252.150:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.