Working its way up from the back of the class: #16,773 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
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
13/ 100
F
Lost ground: down 12,385 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in wipe hold (A+); momentum 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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WWW
·W·····
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Tuesday 3 November, 11:31 UTC, in 4d 13h.
Its weekly schedule tag · low confidence
usual gap0.9 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd
Coming wipes
4d 13hTue 3 Nov, 11:31 UTC
6d 20hThu 5 Nov, 19:00 UTCFW
11d 13hTue 10 Nov, 11:31 UTC
18d 13hTue 17 Nov, 11:31 UTC
25d 13hTue 24 Nov, 11:31 UTC
32d 13hTue 1 Dec, 11:31 UTC
34d 20hThu 3 Dec, 19:00 UTCFW
39d 13hTue 8 Dec, 11:31 UTC
The first 48 hours of its last wipes
Tue 29 SepSun 27 SepSat 26 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, 11:31 UTC30d ago
1
–
running
1
Sun 27 Sep, 07:47 UTC32d ago
2
✓ held half
2.2 days
2
Sat 26 Sep, 09:48 UTC33d ago
2
–
0.9 days
0
Fri 25 Sep, 14:19 UTC34d ago
2
–
0.8 days
1
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 testing. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 185.189.255.249:35400.
Is testing up, and how steady is its uptime?
You cannot join now: testing is offline, last seen 29 days 5 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 20 September 2026.
On what Rust version does testing sit?
The server testing is on Rust network protocol 2633 and build 165217 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does testing wipe its map?
Too few wipes on testing are recorded to confirm the schedule, so its tag guides the prediction. Expect the next wipe on Tuesday 3 November at 11:31 UTC. The world it runs now was created 30 days 10 hours. Wipes are scheduled weekly, according to its tags.
What should you expect from wipe day on testing?
Recent wipes have peaked at 2 players on average. Peak numbers came 1 hours into the latest wipe. Half the peak held until the next wipe in 100% of its recent wipes.
Population
Where does testing place in the wider field of Rust servers?
Over the last seven days, testing has #16,773 for player hours, in the top 70% of all ranked servers.
Is testing a busy server?
It has been 29 days 5 hours since testing was last seen, and it is offline right now.
Tags
What do testing's tags stand for?
You'll see testing tagged with gmvanilla (Game mode): You play vanilla survival here; mp50 (Max players): Its slot count is 50; ts5 (Group limit): Teams cap out at 5; 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): No region code has been set; ^w (Weekly): It wipes weekly; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded 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.
Where does testing appear in the Rust Server Score lists and filters?
Rust Server Score lists that include testing: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
Rules and settings
How is testing set up, and what rules does it keep?
You will find no gather rate in the name of testing. A group here can reach 5 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on testing?
A procedural map of size 2,500 and seed 53296983, generated by the game, is what testing runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
How should you connect to testing?
To connect, start Rust, press F1, and type client.connect 185.189.255.249:35400. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,^w,gmvanilla,cs165217,ts5,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp50
Max playersIts slot count is 50.
ts5
Group limitTeams cap out at 5.
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 codeNo region code has been set.
Wipe schedule
^w
WeeklyIt wipes weekly.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 wipe hold (A+); momentum is the one to work on (F).