Fig. 1Players on [RU] KEDRO - X2 | SOLO | TelegramRG-S2541-01 · Sheet 1 of 12
Fig. 2
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S2541-02 · Sheet 2 of 12
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 11% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S2541-03 · Sheet 3 of 12
Schedule
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 8d 8h.
The force wipe · high confidence
usual gap0.9 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak4players, last three wipes
crowd held100%of its cycles kept half the crowd
Coming wipes
8d 8hThu 5 Nov, 19:00 UTCFW
36d 8hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 22 OctSun 11 OctSat 10 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 4, 1 hours in.
ScheduleExpected wipesRG-S2541-04 · Sheet 4 of 12
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 16:04 UTC5d ago
4
–
running
2
Sun 11 Oct, 10:48 UTC17d ago
4
held half
11.2 days
0
Sat 10 Oct, 10:43 UTC18d ago
3
–
1 days
0
Fri 9 Oct, 13:47 UTC18d ago
1
–
0.9 days
1
Thu 8 Oct, 22:16 UTC19d ago
2
–
0.6 days
1
Thu 8 Oct, 11:43 UTC19d ago
2
–
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.
Table 1Wipe logRG-S2541-05 · Sheet 5 of 12
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
What uptime is recorded for [RU] KEDRO - X2 | SOLO | Telegram, and is it up?
At this moment [RU] KEDRO - X2 | SOLO | Telegram is online. About 2 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. First seen by Rust Graphs on 8 October 2026.
2.
What does the recorded performance of [RU] KEDRO - X2 | SOLO | Telegram show?
The last 48 hours give an average of 24 server fps and a floor of 9. Counted at its highest: 111,772 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 3,441 MB. What players feel as lag is low fps together with a climbing entity count.
3.
In which location is [RU] KEDRO - X2 | SOLO | Telegram hosted?
No region tag is published by [RU] KEDRO - X2 | SOLO | Telegram, but its name points to Europe. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 31.77.232.53:28015 is its address.
4.
What Rust version is recorded for [RU] KEDRO - X2 | SOLO | Telegram?
Rust network protocol 2635 and build 168909 on Linux: that is what [RU] KEDRO - X2 | SOLO | Telegram runs. Steam updates your game, which must be on the same protocol for you to join.
Counts
5.
How many players are plotted on [RU] KEDRO - X2 | SOLO | Telegram?
At the last refresh, [RU] KEDRO - X2 | SOLO | Telegram recorded 4 players across 75 slots. The seven-day mean is 2 players; the peak over the same period is 7. Averaged over the last 48 hours, the player count is highest at 12:00 UTC: 6 players.
6.
What rank has been recorded for [RU] KEDRO - X2 | SOLO | Telegram?
Over the last seven days, [RU] KEDRO - X2 | SOLO | Telegram records #2,541 for player hours: the top 11% of all ranked servers.
Wipe data
7.
On [RU] KEDRO - X2 | SOLO | Telegram, what does the data show for wipe day?
At their busiest, its recent wipes drew 4 players on average. 1 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 100% of its recent wipes stayed above half that peak.
8.
On [RU] KEDRO - X2 | SOLO | Telegram, when do wipes occur?
The force wipe is the only wipe at [RU] KEDRO - X2 | SOLO | Telegram, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. 5 days 18 hours ago the current world was made. Its tags give a wipe schedule of one wipe per month.
Rules and settings
9.
Which settings does [RU] KEDRO - X2 | SOLO | Telegram run, and what rules?
2x gather is stated in the name of [RU] KEDRO - X2 | SOLO | Telegram. Eight players per group: the default for the game. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it as Modded. Plugins run: Oxide. Anti-cheat: VAC, from Valve, is on.
10.
What is the map for [RU] KEDRO - X2 | SOLO | Telegram?
[RU] KEDRO - X2 | SOLO | Telegram runs a procedural map of size 4,000 with seed 1337, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. Recorded map name: Custom Map.
Tags
11.
Where does [RU] KEDRO - X2 | SOLO | Telegram appear among the Rust Graphs lists and filters?
These Rust Graphs lists include [RU] KEDRO - X2 | SOLO | Telegram: Servers with a 2x gather rate, Europe servers, plotted and Modded Rust servers. It is returned by 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.
12.
Which meaning is attached to each tag on [RU] KEDRO - X2 | SOLO | Telegram?
gmrust (Game mode): Standard survival, as Rust plays; mp75 (Max players): Slots: 75; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^m (Monthly): Monthly wipes, on Facepunch's force wipe; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded are the tags [RU] KEDRO - X2 | SOLO | Telegram publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
13.
Who is the operator of [RU] KEDRO - X2 | SOLO | Telegram?
No other server we track uses the in2rl.com hostname that [RU] KEDRO - X2 | SOLO | Telegram publishes.
Connect
14.
What is the way to connect to [RU] KEDRO - X2 | SOLO | Telegram?
Enter client.connect 31.77.232.53:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.
NotesAnswered from the figuresRG-S2541-11 · Sheet 11 of 12
Key
Server tags
what each one means
Published asmp75,ptrak,$r?,v2635,^m,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeStandard survival, as Rust plays.
mp75
Max playersSlots: 75.
ts8
Group limitTeams are capped at 8, the default setting.
v2635
ProtocolJoin only if your game is on protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeRegion code not set.
Wipe schedule
^m
MonthlyMonthly wipes, on Facepunch's force wipe.
Mods and access
^o
OxideThe plugin framework is Oxide (uMod).
^z
ModdedPlugins or settings change the game, so it is listed under Modded.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
