Fig. 1Players on CHYRKA RUST #1 | X2 | One GridRG-S15388-01 · Sheet 1 of 11
Fig. 2
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Fig. 2FPS, entities and memoryRG-S15388-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers, and #527 of the trio servers (top 83%). Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S15388-03 · Sheet 3 of 11
Schedule
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap2.2 daysbetween real wipes
on rhythm38%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 1
The first 48 hours of its last wipes
Tue 20 OctSun 18 OctSat 17 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
ScheduleExpected wipesRG-S15388-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 20 Oct, 12:01 UTC9d ago
0
–
running
0
Sun 18 Oct, 10:36 UTC11d ago
1
halved by day 1
2.1 days
0
Sat 17 Oct, 12:01 UTC12d ago
1
–
0.9 days
0
Thu 15 Oct, 16:38 UTC13d ago
1
–
1.8 days
0
Tue 13 Oct, 10:31 UTC16d ago
2
held half
2.3 days
0
Mon 12 Oct, 20:31 UTC16d ago
2
–
0.6 days
0
Sat 10 Oct, 12:01 UTC19d ago
1
held half
2.4 days
0
Tue 6 Oct, 12:00 UTC23d ago
0
–
4 days
0
Sat 3 Oct, 12:01 UTC26d ago
2
halved by day 2
3 days
0
Tue 29 Sep, 12:00 UTC30d ago
0
–
4 days
0
Sat 26 Sep, 12:00 UTC33d ago
2
halved by day 2
3 days
0
Tue 22 Sep, 12:00 UTC37d ago
1
halved by day 2
4 days
0
Sat 19 Sep, 12:02 UTC40d ago
3
held half
3 days
0
Tue 15 Sep, 12:01 UTC44d ago
1
halved by day 1
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-S15388-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
What uptime is recorded for CHYRKA RUST #1 | X2 | One Grid, and is it up?
CHYRKA RUST #1 | X2 | One Grid is offline at this moment; 8 days 16 hours ago is when it was last seen. 0 of 168 hours up over the last 7 full days, which is 0% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
2.
In which location is CHYRKA RUST #1 | X2 | One Grid hosted?
No region is published by CHYRKA RUST #1 | X2 | One Grid. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 65.108.194.241:29001 is its address.
3.
What Rust version is recorded for CHYRKA RUST #1 | X2 | One Grid?
On Linux, CHYRKA RUST #1 | X2 | One Grid runs Rust network protocol 2634 and build 167781. The same protocol is required for joining, and Steam updates your game to it.
Counts
4.
What does the population history show for CHYRKA RUST #1 | X2 | One Grid?
The latest refresh records CHYRKA RUST #1 | X2 | One Grid as offline, last seen 8 days 16 hours ago.
5.
What rank has been recorded for CHYRKA RUST #1 | X2 | One Grid?
Player hours over seven days place CHYRKA RUST #1 | X2 | One Grid at #15,388, within the top 70% of ranked servers. #527 against other trio servers.
Wipe times
6.
What happens on CHYRKA RUST #1 | X2 | One Grid on the day of a wipe?
At their busiest, its recent wipes drew 1 players on average. 0 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 50% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 1.
7.
Which times and days are wipes plotted at on CHYRKA RUST #1 | X2 | One Grid?
CHYRKA RUST #1 | X2 | One Grid wipes at times that follow no pattern, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. 9 days ago the current world was made.
Settings
8.
Which rules and settings are recorded for CHYRKA RUST #1 | X2 | One Grid?
The name records 2x gather for CHYRKA RUST #1 | X2 | One Grid. A group tops out at 3 players (trio). It runs the survival game mode, the standard game: gather, build, raid. PvP and raiding are on. The server browser lists it under Modded: plugins or settings change the game. The plugin count is Oxide. Anti-cheat: VAC, from Valve, is on.
9.
What is the map for CHYRKA RUST #1 | X2 | One Grid?
Size 4,500 with seed 1337: that is the procedural map CHYRKA RUST #1 | X2 | One Grid runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The name of the map reads: Custom Map.
Tags
10.
On Rust Graphs, which lists and filters contain CHYRKA RUST #1 | X2 | One Grid?
The Rust Graphs lists that carry CHYRKA RUST #1 | X2 | One Grid are: Servers with a 2x gather rate, Modded Rust servers and Trio Rust servers, plotted live. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Trio; Last wipe: In the last 2 weeks; Gather rate: 2x.
11.
Which meaning is attached to each tag on CHYRKA RUST #1 | X2 | One Grid?
The game's server browser reads these tags from CHYRKA RUST #1 | X2 | One Grid: gmrust (Game mode): Survival in standard Rust style; mp75 (Max players): 75 player slots; ts3 (Group limit): Teams hold no more than 3; v2634 (Protocol): Your game must match protocol 2634 to join; cs167781 (Build): 167781 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; jp0 (Custom tag): The owner or a plugin set this tag; it is not standard Rust. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Joining the server
12.
How is CHYRKA RUST #1 | X2 | One Grid joined?
In Rust, press F1 and type client.connect 65.108.194.241:29001 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. You will find its website at https://discord.com/invite/qZWs5kyDV7.
NotesAnswered from the figuresRG-S15388-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp75,ptrak,jp0,$r?,v2634,gmrust,cs167781,ts3,^o^z
Game
gmrust
Game modeSurvival in standard Rust style.
mp75
Max players75 player slots.
ts3
Group limitTeams hold no more than 3.
v2634
ProtocolYour game must match protocol 2634 to join.
cs167781
Build167781 is the game build.
ptrak
NetworkingStandard network layer: RakNet.
$r?
Region codeNo region code is recorded.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is Modded.
Other
jp0
Custom tagThe owner or a plugin set this tag; it is not standard Rust.
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.
KeyTag string decodedRG-S15388-11 · Sheet 11 of 11