Working its way up from the back of the class: #16,275 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
49/ 100
D
Slipped a little: down 378 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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 28 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
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 6d 20h.
The force wipe · high confidence
wipe-day peak0players, last three wipes
Coming wipes
6d 20hThu 5 Nov, 19:00 UTCFW
34d 20hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
No hourly players around its wipes yet.
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
Thu 1 Oct, 17:03 UTCFW28d ago
0
–
running
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
The name of RustSB - Staging测试服务器 points to Asia, though no region tag is set. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 120.220.76.192:44015.
How dependable is RustSB - Staging测试服务器, and is it online at the moment?
You cannot join now: RustSB - Staging测试服务器 is offline, last seen 28 days 5 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 28 September 2026, Rust Server Score saw it for the first time.
On what Rust version does RustSB - Staging测试服务器 sit?
Rust network protocol 2634 and build 166493 on Windows is what RustSB - Staging测试服务器 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does RustSB - Staging测试服务器 wipe its map?
Once a month, RustSB - Staging测试服务器 wipes with the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 28 days 5 hours.
What should you expect from wipe day on RustSB - Staging测试服务器?
The average peak on its recent wipes was 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Population
Where does RustSB - Staging测试服务器 sit among Rust servers?
Over the last seven days, RustSB - Staging测试服务器 has #16,275 for player hours, in the top 69% of all ranked servers.
How many players does RustSB - Staging测试服务器 usually have?
The last sighting of RustSB - Staging测试服务器 was 28 days 5 hours ago, and it is offline right now.
Tags
What do RustSB - Staging测试服务器's tags stand for?
The game's browser takes its cue from the tags RustSB - Staging测试服务器 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp500 (Max players): 500 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166493 (Build): Build number: 166493; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does RustSB - Staging测试服务器 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count RustSB - Staging测试服务器 among them: Best community servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
Which rules does RustSB - Staging测试服务器 enforce, and what are its settings?
You will find no gather rate in the name of RustSB - Staging测试服务器. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map RustSB - Staging测试服务器 uses?
RustSB - Staging测试服务器 runs a game-generated procedural map at size 4,900, seed 238479. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join RustSB - Staging测试服务器?
Enter client.connect 120.220.76.192:44015 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 asmp500,ptrak,$r?,v2634,gmrust,cs166493,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp500
Max players500 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166493
BuildBuild number: 166493.
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. Strongest in momentum (D); standing is the one to work on (F).