Offline 136.36.100.238:28015 checked 31d ago
Rust Server Test
Connect
srv = rust.server("136.36.100.238:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 26 Sep, 18:39 UTC32d ago | 0 | NaN | running | 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 136.36.100.238:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Sep 2026, 18:39 UTC
- hostname
- –
- first seen
- 20 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 552 on average | 636/675 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 485/525 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 299 on average | 59/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 298 on average | 36/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 271 on average | 138/200 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 254 on average | 255/300 |
Quick answers
From the figures on this page.
Population
What position does Rust Server Test take in the server rankings?
Over the last seven days Rust Server Test sits at #16,733 on player hours, in the top 71% of ranked servers.
What population does Rust Server Test carry?
Rust Server Test returns no live count at this refresh, having last been seen 31 days 22 hours ago.
Server data
Which Rust version is Rust Server Test on?
The build is Rust network protocol 2633 and build 165217 on Windows, run by Rust Server Test. The protocol has to match before you can join, and Steam does the updating.
Is Rust Server Test up, and what does its uptime show?
The latest sample has Rust Server Test offline, with a last sighting 31 days 22 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 20 September 2026.
In which location is Rust Server Test hosted?
No region is published by Rust Server Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 136.36.100.238:28015.
Settings and map
Which settings and rules does Rust Server Test run?
The name Rust Server Test carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.
Which map has Rust Server Test selected?
A procedural map runs on Rust Server Test, generated by the game.
Wipe schedule
When does Rust Server Test wipe, and on what schedule?
A rhythm cannot be read from the wipes of Rust Server Test on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 32 days 1 hours ago.
On Rust Server Test, what happens on wipe day?
The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which lists on Rust Data hold Rust Server Test, and which filters?
These Rust Data lists include Rust Server Test: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on Rust Server Test?
Read by the game's server browser, the tags Rust Server Test publishes are: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): Slot count: 2; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): The server runs build 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to Rust Server Test?
Enter client.connect 136.36.100.238:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.