Statistical profileOffline
Rust Server [Docker] Test
104.7.174.182:28015 checked 44d ago
Connect to this server
1. Main points
Players now
0/ 5
0% full
7-day average
0
peak –
Rank
#15,172
no region published
Last wipe
52d ago
no schedule published
Next wipe
–
no wipe seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 5 slots.
- It ranks #15,172 of all ranked servers, on player hours over the last seven days.
- Its current map went up 52d ago.
2. Players
Figure 1: Players on Rust Server [Docker] Test
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Source: Live server queries, Rust Census
5. Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 4: Map of Rust Server [Docker] Test
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of Rust Server [Docker] Test
What the server publishes and what was recorded
| Address | 104.7.174.182:28015 |
|---|---|
| Region | – |
| Max players | 5 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 5 Sep 2026, 16:57 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 156 on average | 127 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 129 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 126 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 51 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 26 / 1000 |
10. Quick answers
From the figures on this page.
Wipe schedule
This release records the wipe timetable for Rust Server [Docker] Test: what is it?
Too few wipes of Rust Server [Docker] Test are on record to establish its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world was generated 52 days 14 hours ago.
Server record
What does the record show for the uptime and current status of Rust Server [Docker] Test?
The latest count records Rust Server [Docker] Test as offline, last seen 44 days 14 hours ago. A total of 0 of 168 hours were up over 7 full days, which is 0% of the time. The first sighting of it by Rust Census was on 13 September 2026.
Which location does Rust Server [Docker] Test run from?
No region is given by Rust Server [Docker] Test. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. 104.7.174.182:28015 is its address.
On which Rust version does Rust Server [Docker] Test operate?
This release lists Rust Server [Docker] Test on Rust network protocol 2633 and build 163493, running on Linux. The same protocol is required for your game to join, and Steam updates it for you.
Player counts
How many players does Rust Server [Docker] Test carry?
Rust Server [Docker] Test is offline at present; its last recording was 44 days 14 hours ago.
What position does Rust Server [Docker] Test hold in the server rankings?
For seven-day player hours, Rust Server [Docker] Test is ranked #15,172, placing it in the top – of all ranked servers.
Lists and tags
On Rust Census, which lists and filters carry Rust Server [Docker] Test?
The Rust Census lists that Rust Server [Docker] Test fits are: Modded Rust servers, counted. Under these filters it comes up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Rust Server [Docker] Test carry?
gmrust (Game mode): The game mode is standard survival as Rust runs it; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): 8 per team, which is the game's default limit; v2633 (Protocol): Protocol 2633 is required; a different version cannot join; cs163493 (Build): Build 163493 is installed; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): This server carries no region code; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings are the tags Rust Server [Docker] Test publishes, and the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Rules, map
Which map is in use on Rust Server [Docker] Test?
The game generates the procedural map on Rust Server [Docker] Test.
How is Rust Server [Docker] Test configured, and what rules does it keep?
The name of Rust Server [Docker] Test carries no gather rate. The group cap stands at 8 players, the default for the game. It runs survival, the standard game: gather, build, raid. Raiding and player combat are permitted. Modded is its section in the server browser, because plugins or settings change the game. Oxide plugins are recorded on it. VAC, Valve's anti-cheat, is enabled.
Connecting
What steps are needed to join Rust Server [Docker] Test?
Enter client.connect 104.7.174.182:28015 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp5,ptrak,$r?,v2633,gmrust,cs163493,ts8,^o^z
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp5 | Max players The server holds 5 slots. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2633 | Protocol Protocol 2633 is required; a different version cannot join. |
cs163493 | Build Build 163493 is installed. |
ptrak | Networking The network layer is RakNet, the game's standard. |
$r? | Region code This server carries no region code. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded Modded: the game is changed by plugins or settings. |
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.