Online 31.77.232.53:28015 checked 10m ago
[RU] KEDRO - X2 | SOLO | Telegram
Connect
srv = rust.server("31.77.232.53:28017")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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, measured since 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 11% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 22h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 22h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 22h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 16:04 UTC6d ago | 4 | NaN | running | 2 |
| 1 | Sun 11 Oct, 10:48 UTC17d ago | 4 | held half | 11.2 days | 0 |
| 2 | Sat 10 Oct, 10:43 UTC18d ago | 3 | NaN | 1 days | 0 |
| 3 | Fri 9 Oct, 13:47 UTC19d ago | 1 | NaN | 0.9 days | 1 |
| 4 | Thu 8 Oct, 22:16 UTC19d ago | 2 | NaN | 0.6 days | 1 |
| 5 | Thu 8 Oct, 11:43 UTC20d ago | 2 | NaN | 0.4 days | 0 |
# 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.
display(srv.map, srv.info())Map
4000 · seed 1337![Map of [RU] KEDRO - X2 | SOLO | Telegram](https://files.facepunch.com/rust/map-images/aa2dc91de39c0c6c88fbe74e6a1fb023fa0eb1384841844f69ed6a1124e40b65/kedro-wipe-2026-10-22.4000.1782786114867.289_aa2dc91de39c0c6c88fbe74e6a1fb023.jpg)
- map
- Custom Map
- size
- 4000
- seed
- 1337
Server
srv.info()- address
- 31.77.232.53:28015
- region
- –
- max players
- 75
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 22 Oct 2026, 16:04 UTC
- hostname
- rust-x2solo.server.in2rl.com
- first seen
- 8 Oct 2026
Operator · in2rl.com
rust.servers(operator="in2rl.com").sort_values("players")| server | players |
|---|
The only server publishing a in2rl.com hostname.
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 782 on average | 802/1000 |
| 1 | Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 585 on average | 533/700 |
| 2 | EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 342 on average | 303/385 |
| 3 | Vitality - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 300 on average | 108/150 |
| 4 | EU Limitless 2x Monthly Main | No BP Wipes | x2 | EU · groups of 12+ · 2x · monthly · 270 on average | 340/410 |
| 5 | MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10 | EU · groups of 300+ · 2x · monthly · 151 on average | 115/500 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does [RU] KEDRO - X2 | SOLO | Telegram rank?
Player hours over seven days put [RU] KEDRO - X2 | SOLO | Telegram at #2,481, in the top 11% of the ranked set.
How full does [RU] KEDRO - X2 | SOLO | Telegram run?
Current row: 2 players on [RU] KEDRO - X2 | SOLO | Telegram, against 75 slots. Over the last seven days it averaged 2 players and peaked at 7. Peak hour in the last 48 hours: 12:00 UTC, mean 6 players.
About the server
How well does [RU] KEDRO - X2 | SOLO | Telegram perform?
The 48-hour average is 22 server fps, with a low of 8. Buildings, deployables and all else in the world took the count as high as 111,820 entities. The memory field tops out at 3,441 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is [RU] KEDRO - X2 | SOLO | Telegram on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by [RU] KEDRO - X2 | SOLO | Telegram. Joining needs the same protocol on your game; Steam handles the update.
How reliable is [RU] KEDRO - X2 | SOLO | Telegram, and is it up?
The current sample puts [RU] KEDRO - X2 | SOLO | Telegram online. Count back 8 hours from its reported uptime to get the last restart. 168 of 168 hours up over the last 7 full days, or 100%. Its earliest recorded date in Rust Data is 8 October 2026.
Which location does [RU] KEDRO - X2 | SOLO | Telegram run from?
The name of [RU] KEDRO - X2 | SOLO | Telegram points to Europe, even though no region tag is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 31.77.232.53:28015.
Settings and map
Which settings and rules does [RU] KEDRO - X2 | SOLO | Telegram run?
2x gather is what the name states, and the name is [RU] KEDRO - X2 | SOLO | Telegram. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has [RU] KEDRO - X2 | SOLO | Telegram loaded?
The game generates the map on [RU] KEDRO - X2 | SOLO | Telegram: procedural, size 4,000, seed 1337. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Custom Map.
Wipe schedule
When does [RU] KEDRO - X2 | SOLO | Telegram wipe, and on what schedule?
Once a month [RU] KEDRO - X2 | SOLO | Telegram wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 6 days 4 hours ago. Its tags carry a monthly wipe schedule.
On [RU] KEDRO - X2 | SOLO | Telegram, what happens on wipe day?
Recent wipes averaged 4 players at their peak. Peak population on the latest wipe came 1 hours in. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Tags and filters
Which Rust Data filters and lists contain [RU] KEDRO - X2 | SOLO | Telegram?
These Rust Data lists include [RU] KEDRO - X2 | SOLO | Telegram: EU Rust servers, Modded Rust servers and 2x Rust servers. It appears under these filters on the server list: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week; Gather rate: 2x.
Which operator runs [RU] KEDRO - X2 | SOLO | Telegram?
Among the servers we track, only [RU] KEDRO - X2 | SOLO | Telegram publishes this in2rl.com hostname.
How should you read the server tags on [RU] KEDRO - X2 | SOLO | Telegram?
Read by the game's server browser, the tags [RU] KEDRO - X2 | SOLO | Telegram publishes are: gmrust (Game mode): Rust survival in its standard form; mp75 (Max players): Slot count: 75; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
How can I connect to [RU] KEDRO - X2 | SOLO | Telegram?
Enter client.connect 31.77.232.53:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.