Working its way up from the back of the class: #16,032 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
39/ 100
F
Slipped a little: down 3,569 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); 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.
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W····
······W
·W·····
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap6.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Tue 29 SepSun 27 SepWed 16 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 29 Sep, 21:44 UTC29d ago
1
–
running
0
Sun 27 Sep, 16:33 UTC31d ago
1
halved by day 1
2.2 days
0
Wed 16 Sep, 16:47 UTC42d ago
0
–
11 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 Rust Beyond | Test Server. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 51.210.34.129:28035.
How dependable is Rust Beyond | Test Server, and is it online at the moment?
You cannot join now: Rust Beyond | Test Server is offline, last seen 27 days 1 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 16 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Rust Beyond | Test Server sit?
Rust network protocol 2633 and build 165217 on Linux is what Rust Beyond | Test Server runs. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does Rust Beyond | Test Server wipe its map?
There is no next wipe to predict on Rust Beyond | Test Server, as it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 28 days 23 hours have passed since this world was made.
What should you expect from wipe day on Rust Beyond | Test Server?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 1 hours after it began. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Player numbers
Where does Rust Beyond | Test Server place in the wider field of Rust servers?
In the top 69% of all ranked servers, Rust Beyond | Test Server sits at #16,032 for player hours over the last seven days.
How many players does Rust Beyond | Test Server usually have?
It has been 27 days 1 hours since Rust Beyond | Test Server was last seen, and it is offline right now.
Tags
What do Rust Beyond | Test Server's tags stand for?
You'll see Rust Beyond | Test Server tagged with gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): This runs on build 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here in the browser, which picks them up from the 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.
Which lists and filters on Rust Server Score show Rust Beyond | Test Server?
These Rust Server Score lists count Rust Beyond | Test Server among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
What settings and rules apply on Rust Beyond | Test Server?
Nothing in the name of Rust Beyond | Test Server states a gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in 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 Carbon. The server runs Valve's anti-cheat, VAC.
Rust Beyond | Test Server runs which map?
A procedural map, generated by the game, is what Rust Beyond | Test Server runs.
Connecting
How do you get onto Rust Beyond | Test Server?
Enter client.connect 51.210.34.129:28035 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 asmp10,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon provides the plugin framework 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 (F); wipes are the one to work on (F).