On the class lists: C− (59), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 2
Rank#9,700top 44%
Last wipe13d agomonthly schedule
Next wipe7d 15hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
56/ 100
C−
Working its way up from the back of the class: #9,700 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
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
21/ 100
F
Lost ground: down 5,655 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in wipe hold (A+); population 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 23 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 44% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····WW
W·W····
···W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h.
The force wipe · high confidence
usual gap1.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak3players, last three wipes
crowd held100%of its cycles kept half the crowd
Coming wipes
7d 15hThu 5 Nov, 19:00 UTCFW
35d 15hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 15 OctWed 7 OctMon 5 Oct
Players each hour, from the hour of the wipe. The latest peaked at 4, 22 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 15:01 UTC13d ago
4
–
running
0
Wed 7 Oct, 16:05 UTC21d ago
2
✓ held half
8 days
2
Mon 5 Oct, 17:27 UTC23d ago
2
–
1.9 days
1
Sun 4 Oct, 10:57 UTC24d ago
2
–
1.3 days
0
Sat 3 Oct, 12:00 UTC25d ago
2
–
1 days
2
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
EU · groups of 12+ · 2x · monthly · 278 on average
64 / 200
Quick answers
from the figures on this page
Server details
In what location does SmallRust | Small map | One grid | Max 2 | X2 sit?
No region is published for SmallRust | Small map | One grid | Max 2 | X2. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 79.120.11.21:28015.
How reliable is SmallRust | Small map | One grid | Max 2 | X2, and is it up?
The server is down: SmallRust | Small map | One grid | Max 2 | X2 is offline now, with the last sighting 6 days 8 hours ago. It was up 12% of the time over the last 7 full days, 20 of 168 hours. On 22 September 2026, Rust Server Score saw it for the first time.
What Rust version is SmallRust | Small map | One grid | Max 2 | X2 on?
The server SmallRust | Small map | One grid | Max 2 | X2 is on Rust network protocol 2634 and build 166652 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does SmallRust | Small map | One grid | Max 2 | X2 wipe its map?
Once a month, SmallRust | Small map | One grid | Max 2 | X2 wipes with the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 13 days 12 hours. Its tags record that it wipes monthly.
What should you expect from wipe day on SmallRust | Small map | One grid | Max 2 | X2?
Recent wipes have peaked at 3 players on average. 22 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 100% of its recent wipes.
Player count
Where does SmallRust | Small map | One grid | Max 2 | X2 place in the wider field of Rust servers?
In the top 44% of all ranked servers, SmallRust | Small map | One grid | Max 2 | X2 sits at #9,700 for player hours over the last seven days.
How many players does SmallRust | Small map | One grid | Max 2 | X2 usually have?
It has been 6 days 8 hours since SmallRust | Small map | One grid | Max 2 | X2 was last seen, and it is offline right now. The seven-day average is 0 players, with a peak of 2.
Lists and filters
How should you read the tags on SmallRust | Small map | One grid | Max 2 | X2?
You'll see SmallRust | Small map | One grid | Max 2 | X2 tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded 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 lists and filters on Rust Server Score show SmallRust | Small map | One grid | Max 2 | X2?
These Rust Server Score lists count SmallRust | Small map | One grid | Max 2 | X2 among them: 2x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks; Gather rate: 2x.
Map and rules
What settings and rules apply on SmallRust | Small map | One grid | Max 2 | X2?
The name of SmallRust | Small map | One grid | Max 2 | X2 points to a 2x gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on SmallRust | Small map | One grid | Max 2 | X2?
A procedural map of size 1,000 and seed 1337, generated by the game, is what SmallRust | Small map | One grid | Max 2 | X2 runs. 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
How do you get onto SmallRust | Small map | One grid | Max 2 | X2?
Enter client.connect 79.120.11.21:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^m,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits 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.
A term to build on. Strongest in wipe hold (A+); population is the one to work on (F).