Working its way up from the back of the class: #16,699 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
47/ 100
D
Slipped a little: down 1,113 places this week. Nothing a good wipe can't fix.
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.
AveragePeak
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 21 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% 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
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
Sun 27 Sep, 10:33 UTC30d 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
You'll find no region listed by IWGamin - Test (Closed). Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 37.200.44.225:28015.
Is IWGamin - Test (Closed) up, and how steady is its uptime?
The server is down: IWGamin - Test (Closed) is offline now, with the last sighting 26 days 23 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 21 September 2026.
Which Rust version is IWGamin - Test (Closed) running?
Rust network protocol 2633 and build 165217 on Linux is what IWGamin - Test (Closed) runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does IWGamin - Test (Closed) wipe, and how often?
There are too few wipes on record for IWGamin - Test (Closed) to show a 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 30 days 11 hours.
What happens on IWGamin - Test (Closed) when wipe day arrives?
The average peak on its recent wipes was 0 players. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does IWGamin - Test (Closed) sit among Rust servers?
In the top 70% of all ranked servers, IWGamin - Test (Closed) sits at #16,699 for player hours over the last seven days.
How many players does IWGamin - Test (Closed) usually have?
It has been 26 days 23 hours since IWGamin - Test (Closed) was last seen, and it is offline right now.
Tags
What is meant by the tags on IWGamin - Test (Closed)?
gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags IWGamin - Test (Closed) publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show IWGamin - Test (Closed)?
These Rust Server Score lists count IWGamin - Test (Closed) among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
What settings and rules apply on IWGamin - Test (Closed)?
Nothing in the name of IWGamin - Test (Closed) states a gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. Vanilla is what it calls itself: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Which map is in play on IWGamin - Test (Closed)?
The game generates the procedural map on IWGamin - Test (Closed) at size 3,500 with seed 12345. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to IWGamin - Test (Closed)?
Enter client.connect 37.200.44.225: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 asmp100,ptrak,$r?,v2633,^v,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max players100 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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).