A full classroom nearly all week: 1 of 1 on average.
Standingrank on player hours
52/ 100
D
Working its way up from the back of the class: #10,771 on player hours.
Uptimehours on the list, last 48
6/ 100
F
Attendance needs work: on the list only 3 of the last 48 hours.
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.
Strongest in population (A+); uptime 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.
AveragePeak
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 48% 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 Testing server. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 95.26.142.128:28015 is the address to use.
Is Testing server up, and how steady is its uptime?
The server is down: Testing server is offline now, with the last sighting 38 hours ago. The first sighting by Rust Server Score was on 27 October 2026.
On what Rust version does Testing server sit?
The server Testing server is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Testing server wipe its map?
The record holds too few of Testing server's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 2 days.
Player count
Where does Testing server sit among Rust servers?
In the top 48% of all ranked servers, Testing server sits at #10,771 for player hours over the last seven days.
What does the population on Testing server look like?
Testing server is offline at the moment; the last time it was seen was 38 hours ago. The seven-day average is 1 players, with a peak of 1. The highest average in the last 48 hours came at 08:00 UTC, with 1 players.
Tags and filters
How should you read the tags on Testing server?
The game's browser takes its cue from the tags Testing server has set: gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. 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 Rust Server Score filters and lists feature Testing server?
Rust Server Score lists that include Testing server: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Server rules
What settings and rules apply on Testing server?
You will find no gather rate in the name of Testing server. 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. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Getting in
How should you connect to Testing server?
Enter client.connect 95.26.142.128: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 asmp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max players1 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it 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 population (A+); uptime is the one to work on (F).