Working its way up from the back of the class: #15,493 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
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 67% of all ranked servers. 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 peak0players, last three wipes
The first 48 hours of its last wipes
No hourly players around its wipes yet.
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 22 Sep, 00:05 UTC35d ago
0
–
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
Which region is RustMods.win | TEST SERVER based in?
No region is published for RustMods.win | TEST SERVER. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 80.89.74.45:28015.
Is RustMods.win | TEST SERVER up, and how steady is its uptime?
You cannot join now: RustMods.win | TEST SERVER is offline, last seen 35 days 21 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 21 September 2026, Rust Server Score saw it for the first time.
On what Rust version does RustMods.win | TEST SERVER sit?
You will find RustMods.win | TEST SERVER on Rust network protocol 2633 and build 164530, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does RustMods.win | TEST SERVER wipe, and how often?
RustMods.win | TEST SERVER has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 35 days 22 hours have passed since this world was made.
What happens on RustMods.win | TEST SERVER when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe.
Player numbers
What position does RustMods.win | TEST SERVER hold in the rankings?
Over the last seven days, RustMods.win | TEST SERVER has #15,493 for player hours, in the top 67% of all ranked servers.
How many players does RustMods.win | TEST SERVER usually have?
The last sighting of RustMods.win | TEST SERVER was 35 days 21 hours ago, and it is offline right now.
Tags
How should you read the tags on RustMods.win | TEST SERVER?
The game's browser takes its cue from the tags RustMods.win | TEST SERVER has set: gmrust (Game mode): Rust survival, played by the standard rules; 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; cs164530 (Build): This runs on build 164530; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here. 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 RustMods.win | TEST SERVER appear in the Rust Server Score lists and filters?
Rust Server Score lists that include RustMods.win | TEST SERVER: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
What settings and rules apply on RustMods.win | TEST SERVER?
You will find no gather rate in the name of RustMods.win | TEST SERVER. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map RustMods.win | TEST SERVER uses?
The game generates a procedural map for RustMods.win | TEST SERVER.
Connecting
What is the way to join RustMods.win | TEST SERVER?
Enter client.connect 80.89.74.45: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 asmp10,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
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.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set 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.