Working its way up from the back of the class: #15,682 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 294 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 gap16.1 daysbetween real wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 5
The first 48 hours of its last wipes
Fri 2 OctTue 15 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 01:13 UTC27d ago
1
–
running
0
Tue 15 Sep, 22:59 UTC43d ago
7
halved by day 5
16.1 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
No region is published for RustServer_12948. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 160.251.252.255:28015.
How dependable is RustServer_12948, and is it online at the moment?
The server is down: RustServer_12948 is offline now, with the last sighting 17 days 15 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 13 September 2026.
On what Rust version does RustServer_12948 sit?
Rust network protocol 2634 and build 166494 on Linux is what RustServer_12948 runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does RustServer_12948 reset?
There are too few wipes on record for RustServer_12948 to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 27 days 12 hours.
What should you expect from wipe day on RustServer_12948?
Across its recent wipes, the busiest moments averaged 4 players. The crowd on the latest wipe was largest 0 hours after it began. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. Day 5 is when it sank below half in the wipes that did not hold.
Population
What position does RustServer_12948 hold in the rankings?
Over the last seven days, RustServer_12948 has #15,682 for player hours, in the top 71% of all ranked servers.
Is RustServer_12948 a busy server?
It has been 17 days 15 hours since RustServer_12948 was last seen, and it is offline right now.
Tags
How should you read the tags on RustServer_12948?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs166494 (Build): This runs on build 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set are the tags RustServer_12948 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 Rust Server Score filters and lists feature RustServer_12948?
These Rust Server Score lists count RustServer_12948 among them: 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.
Server rules
What settings and rules apply on RustServer_12948?
Nothing in the name of RustServer_12948 states a gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. 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_12948?
RustServer_12948 runs a game-generated procedural map at size 4,999, seed 1337. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to RustServer_12948?
Enter client.connect 160.251.252.255: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,gmrust,cs166494,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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).