Working its way up from the back of the class: #15,854 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
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A term to build on.
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.
No daily history yet.
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
No region is published for RustServer_4948. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 133.117.74.185:28015.
How reliable is RustServer_4948, and is it up?
You cannot join now: RustServer_4948 is offline, last seen 20 days 3 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 9 October 2026, Rust Server Score saw it for the first time.
Which Rust version is RustServer_4948 running?
Rust network protocol 2597 and build 130842 on Linux is what RustServer_4948 runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does RustServer_4948 wipe its map?
The record holds too few of RustServer_4948's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 20 days 3 hours have passed since this world was made.
Player numbers
Where does RustServer_4948 sit among Rust servers?
Over the last seven days, RustServer_4948 has #15,854 for player hours, in the top 72% of all ranked servers.
Is RustServer_4948 a busy server?
RustServer_4948 is offline at the moment; the last time it was seen was 20 days 3 hours ago.
Lists and filters
How should you read the tags on RustServer_4948?
You'll see RustServer_4948 tagged with gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): Its slot count is 50; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2597 (Protocol): To get in, your game needs to be on the same version: the protocol is 2597; cs130842 (Build): This runs on build 130842; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server in the browser, which picks them up from the server. 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_4948?
Rust Server Score lists that include RustServer_4948: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does RustServer_4948 enforce, and what are its settings?
Nothing in the name of RustServer_4948 states a gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on RustServer_4948?
RustServer_4948 runs a procedural map, which the game generates.
Getting in
How do you get onto RustServer_4948?
Enter client.connect 133.117.74.185: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?,v2597,gmrust,cs130842,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersIts slot count is 50.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2597
ProtocolTo get in, your game needs to be on the same version: the protocol is 2597.
cs130842
BuildThis runs on build 130842.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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.