Working its way up from the back of the class: #16,850 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
32/ 100
F
Lost ground: down 6,175 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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 71% of all ranked servers, and #490 of the trio servers (top 84%). Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 27 Sep, 00:10 UTC32d ago
1
–
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
RustWerk | LOCAL TEST leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 84.115.215.17:28015 is the address to use.
Is RustWerk | LOCAL TEST up, and how steady is its uptime?
The server is down: RustWerk | LOCAL TEST is offline now, with the last sighting 29 days 23 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 27 September 2026, Rust Server Score saw it for the first time.
On what Rust version does RustWerk | LOCAL TEST sit?
Rust network protocol 2633 and build 165217 on Windows is what RustWerk | LOCAL TEST runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does RustWerk | LOCAL TEST wipe, and how often?
RustWerk | LOCAL TEST has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 32 days 21 hours.
What happens on RustWerk | LOCAL TEST when wipe day arrives?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does RustWerk | LOCAL TEST place in the wider field of Rust servers?
In the top 71% of all ranked servers, RustWerk | LOCAL TEST sits at #16,850 for player hours over the last seven days. It comes #490 among servers in the trio group.
What does the population on RustWerk | LOCAL TEST look like?
RustWerk | LOCAL TEST is offline at the moment; the last time it was seen was 29 days 23 hours ago.
Lists and filters
How should you read the tags on RustWerk | LOCAL TEST?
You'll see RustWerk | LOCAL TEST tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): The server holds 100 slots; ts3 (Group limit): No team may go above 3; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does RustWerk | LOCAL TEST appear in the Rust Server Score lists and filters?
These Rust Server Score lists count RustWerk | LOCAL TEST among them: Modded Rust servers, graded and Rust servers with a trio group limit. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: Trio.
Server rules
What settings and rules apply on RustWerk | LOCAL TEST?
The name of RustWerk | LOCAL TEST gives no gather rate. The cap on group size is 3 players (trio). It runs survival, 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. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
RustWerk | LOCAL TEST runs which map?
RustWerk | LOCAL TEST runs a procedural map, which the game generates.
Connecting
How do you get onto RustWerk | LOCAL TEST?
To connect, start Rust, press F1, and type client.connect 84.115.215.17:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,gmrust,cs165217,ts3,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersThe server holds 100 slots.
ts3
Group limitNo team may go above 3.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: Carbon.
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. Even marks across the subjects, from F to F.