Working its way up from the back of the class: #15,519 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 434 places this week.
A term to build on.
Strongest in momentum (D); wipes are 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 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
····W··
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap7 daysbetween real wipes
wipe-day peak8players, last three wipes
crowd held0%else halves by day 3
The first 48 hours of its last wipes
Fri 25 SepFri 18 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 28 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 25 Sep, 12:02 UTC34d ago
1
–
running
0
Fri 18 Sep, 11:52 UTC41d ago
16
halved by day 3
7 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
You'll find no region listed by RustServer_22939. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 133.88.119.137:28015.
How dependable is RustServer_22939, and is it online at the moment?
At this moment, RustServer_22939 is offline; the last time it was seen was 17 days ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
What Rust version is RustServer_22939 on?
Rust network protocol 2633 and build 165217 on Linux is what RustServer_22939 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does RustServer_22939 wipe, and how often?
RustServer_22939 has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 34 days 4 hours.
What should you expect from wipe day on RustServer_22939?
Recent wipes have peaked at 8 players on average. 28 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 3 is when it sank below half in the wipes that did not hold.
Player numbers
Where does RustServer_22939 place in the wider field of Rust servers?
In the top 71% of all ranked servers, RustServer_22939 sits at #15,519 for player hours over the last seven days.
Is RustServer_22939 a busy server?
RustServer_22939 is offline at the moment; the last time it was seen was 17 days ago.
Tags and filters
What is meant by the tags on RustServer_22939?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): Build number: 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here are the tags RustServer_22939 publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show RustServer_22939?
These Rust Server Score lists count RustServer_22939 among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
What settings and rules apply on RustServer_22939?
You will find no gather rate in the name of RustServer_22939. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
RustServer_22939 runs which map?
RustServer_22939 runs a game-generated procedural map at size 3,500, seed 1602722670. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to RustServer_22939?
To connect, start Rust, press F1, and type client.connect 133.88.119.137:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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 momentum (D); wipes are the one to work on (F).