Working its way up from the back of the class: #13,591 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
21/ 100
F
Lost ground: down 7,992 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 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 62% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
··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.
usual gap4.2 daysbetween real wipes
wipe-day peak4players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Wed 7 OctSat 3 Oct
Players each hour, from the hour of the wipe. The latest peaked at 4, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 7 Oct, 10:40 UTC22d ago
4
–
running
0
Sat 3 Oct, 06:34 UTC26d ago
4
✓ held half
4.2 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
No region is published for crom_rust_test. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 180.20.143.169:28015 is the address to use.
How reliable is crom_rust_test, and is it up?
At this moment, crom_rust_test is offline; the last time it was seen was 11 days 23 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 18 September 2026, Rust Server Score saw it for the first time.
What Rust version is crom_rust_test on?
The server crom_rust_test is on Rust network protocol 2634 and build 167781 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does crom_rust_test wipe, and how often?
There are too few wipes on record for crom_rust_test 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. 22 days 3 hours have passed since this world was made.
What should you expect from wipe day on crom_rust_test?
The average peak on its recent wipes was 4 players. Peak numbers came 1 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 100% of its recent wipes.
Player numbers
Where does crom_rust_test place in the wider field of Rust servers?
Over the last seven days, crom_rust_test has #13,591 for player hours, in the top 62% of all ranked servers.
Is crom_rust_test a busy server?
It has been 11 days 23 hours since crom_rust_test was last seen, and it is offline right now.
Tags and filters
What do crom_rust_test's tags stand for?
You'll see crom_rust_test tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): Its slot count is 10; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: 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. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does crom_rust_test appear in the Rust Server Score lists and filters?
These Rust Server Score lists count crom_rust_test 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
Which rules does crom_rust_test enforce, and what are its settings?
You will find no gather rate in the name of crom_rust_test. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on crom_rust_test?
A procedural map of size 4,000 and seed 179845, generated by the game, is what crom_rust_test 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 do you get onto crom_rust_test?
To connect, start Rust, press F1, and type client.connect 180.20.143.169:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersIts slot count is 10.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: 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).