On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 300% full
7-day average0peak –
Rank#15,339top 69%
Last wipe118d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 30 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,339 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 235 server fps on average.
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 214 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (A+); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 69% 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
Rust test server_1 leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 163.44.113.12:28015.
How dependable is Rust test server_1, and is it online at the moment?
Right now, Rust test server_1 is online. The uptime it reports puts the last restart at about 12 days 22 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Does Rust test server_1 perform well?
The average over the last 48 hours was 235 server fps, and it never went below 221. At its peak, it held 3,122 entities, including buildings, deployables and all else in the world. At its highest, it used 5,694 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does Rust test server_1 sit?
You will find Rust test server_1 on Rust network protocol 2631 and build 156583, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does Rust test server_1 wipe, and how often?
There are too few wipes on record for Rust test server_1 to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 118 days 6 hours have passed since this world was made.
Population
Where does Rust test server_1 place in the wider field of Rust servers?
Over the last seven days, Rust test server_1 has #15,339 for player hours, in the top 69% of all ranked servers.
How many players does Rust test server_1 usually have?
With 30 slots available, Rust test server_1 currently has 0 players. For the last seven days, the average number of players was 0.
Lists and filters
What do Rust test server_1's tags stand for?
You'll see Rust test server_1 tagged with gmrust (Game mode): Survival in the standard Rust style; mp30 (Max players): 30 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2631 (Protocol): The game protocol is 2631, so your game must match that version to join; cs156583 (Build): Build number: 156583; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Rust test server_1 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Rust test server_1 among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is Rust test server_1 set up, and what rules does it keep?
The name of Rust test server_1 gives no gather rate. The default of 8 players applies as the group cap. 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 Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Rust test server_1 uses?
Rust test server_1 runs a game-generated procedural map at size 1,000, seed 1319438048. 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 Rust test server_1?
Enter client.connect 163.44.113.12: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 asmp30,ptrak,$r?,v2631,gmrust,cs156583,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp30
Max players30 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2631
ProtocolThe game protocol is 2631, so your game must match that version to join.
cs156583
BuildBuild number: 156583.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).