Working its way up from the back of the class: #15,388 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
29/ 100
F
Lost ground: down 6,514 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in wipe hold (D); momentum is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
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.
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.
Attendance: the wipe record
14 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W···W·
·W···W·
·W···W·
·W···W·
WW·W·WW
·W·····
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is CHYRKA RUST #1 | X2 | One Grid based in?
CHYRKA RUST #1 | X2 | One Grid leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 65.108.194.241:29001.
How reliable is CHYRKA RUST #1 | X2 | One Grid, and is it up?
At this moment, CHYRKA RUST #1 | X2 | One Grid is offline; the last time it was seen was 8 days 16 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
What Rust version is CHYRKA RUST #1 | X2 | One Grid on?
Rust network protocol 2634 and build 167781 on Linux is what CHYRKA RUST #1 | X2 | One Grid runs. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does CHYRKA RUST #1 | X2 | One Grid reset?
No next wipe can be predicted for CHYRKA RUST #1 | X2 | One Grid, which wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 9 days.
What happens on CHYRKA RUST #1 | X2 | One Grid when wipe day arrives?
Recent wipes have peaked at 1 players on average. 0 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 50% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Player numbers
Where does CHYRKA RUST #1 | X2 | One Grid place in the wider field of Rust servers?
Over the last seven days, CHYRKA RUST #1 | X2 | One Grid has #15,388 for player hours, in the top 70% of all ranked servers. In the trio group, it ranks #527.
What does the population on CHYRKA RUST #1 | X2 | One Grid look like?
The last sighting of CHYRKA RUST #1 | X2 | One Grid was 8 days 16 hours ago, and it is offline right now.
Lists and filters
What do CHYRKA RUST #1 | X2 | One Grid's tags stand for?
You'll see CHYRKA RUST #1 | X2 | One Grid tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp75 (Max players): 75 slots are available; ts3 (Group limit): No team may go above 3; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; jp0 (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature CHYRKA RUST #1 | X2 | One Grid?
Rust Server Score lists that include CHYRKA RUST #1 | X2 | One Grid: 2x Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Trio; Last wipe: In the last 2 weeks; Gather rate: 2x.
Server rules
How is CHYRKA RUST #1 | X2 | One Grid set up, and what rules does it keep?
CHYRKA RUST #1 | X2 | One Grid sets gather at 2x, as its name suggests. You can have up to 3 players in a group (trio). survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
CHYRKA RUST #1 | X2 | One Grid runs which map?
The game generates the procedural map on CHYRKA RUST #1 | X2 | One Grid at size 4,500 with seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
How to join
What is the way to join CHYRKA RUST #1 | X2 | One Grid?
Enter client.connect 65.108.194.241:29001 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/qZWs5kyDV7.
Server tags
what each one means
Published asmp75,ptrak,jp0,$r?,v2634,gmrust,cs167781,ts3,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp75
Max players75 slots are available.
ts3
Group limitNo team may go above 3.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Other
jp0
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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.
A term to build on. Strongest in wipe hold (D); momentum is the one to work on (F).