Working its way up from the back of the class: #15,983 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
53/ 100
D
Moving up: up 938 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
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 71% 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 Test Server RaidSim. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 187.13.28.14:28021.
How reliable is Test Server RaidSim, and is it up?
At this moment, Test Server RaidSim is offline; the last time it was seen was 23 days 12 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 5 October 2026.
Which Rust version is Test Server RaidSim running?
The server Test Server RaidSim is on Rust network protocol 2634 and build 166494 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Test Server RaidSim reset?
There are too few wipes on record for Test Server RaidSim 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. The world it runs now was created 23 days 13 hours.
Population
What position does Test Server RaidSim hold in the rankings?
Over the last seven days, Test Server RaidSim has #15,983 for player hours, in the top 71% of all ranked servers.
How many players does Test Server RaidSim usually have?
Test Server RaidSim is offline at the moment; the last time it was seen was 23 days 12 hours ago.
Tags and filters
What do Test Server RaidSim's tags stand for?
You'll see Test Server RaidSim tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp3 (Max players): 3 slots are available; ts100 (Group limit): Teams cap out at 100; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): This runs on build 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^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.
Which lists and filters on Rust Server Score show Test Server RaidSim?
These Rust Server Score lists count Test Server RaidSim among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
How is Test Server RaidSim set up, and what rules does it keep?
Nothing in the name of Test Server RaidSim states a gather rate. You can play in groups of up to 100 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Connecting
How should you connect to Test Server RaidSim?
Enter client.connect 187.13.28.14:28021 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 asmp3,ptrak,$r?,v2634,gmrust,cs166494,ts100,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp3
Max players3 slots are available.
ts100
Group limitTeams cap out at 100.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
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 term to build on. Strongest in momentum (D); standing is the one to work on (F).