Offline 31.23.230.110:28015 checked 5d ago
Evil_Test
Connect
srv = rust.server("31.23.230.110: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, measured since 24 Oct. 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 bestTop 54% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h. # The force wipe
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
5250 · seed 1337
- map
- Procedural Map
- size
- 5250
- seed
- 1337
Server
srv.info()- address
- 31.23.230.110:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 20 Oct 2026, 22:14 UTC
- hostname
- –
- first seen
- 24 Oct 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 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 43/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 91 on average | 133/700 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 17/1000 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 76 on average | 98/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 73 on average | 207/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 29.10 | EU · groups of 16+ · monthly · 69 on average | 342/1000 |
Quick answers
From the figures on this page.
Population
How does Evil_Test compare in the rankings?
Over the last seven days Evil_Test sits at #12,012 on player hours, in the top 54% of ranked servers.
What population does Evil_Test carry?
The current row shows Evil_Test offline; the last response was 5 days 2 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server facts
Which Rust version is Evil_Test on?
Rust network protocol 2635 and build 168909 on Windows is what Evil_Test runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Evil_Test, and is it online now?
The latest sample has Evil_Test offline, with a last sighting 5 days 2 hours ago. Over the last 4 full days the hours up number 0 of 96, 0%. Rust Data logged it first on 24 October 2026.
In which location is Evil_Test hosted?
For Evil_Test, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 31.23.230.110:28015.
Map and rules
Which settings and rules does Evil_Test run?
The name Evil_Test carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has Evil_Test loaded?
Evil_Test runs a procedural map of size 5,250 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does Evil_Test wipe, and on what schedule?
The next wipe for Evil_Test is an estimate, drawn from the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 8 days 22 hours ago, and that is the one in play. Its tags carry a monthly wipe schedule.
Tags, lists
Which Rust Data filters and lists contain Evil_Test?
On Rust Data, Evil_Test appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks.
How should you read the server tags on Evil_Test?
The game's server browser reads these tags from Evil_Test: gmvanilla (Game mode): The mode is vanilla survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way into Evil_Test?
In Rust, F1 opens the console: type client.connect 31.23.230.110:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.