Online 185.186.143.156:28015 checked 10m ago
zombie-test
Connect
srv = rust.server("185.186.143.156: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 14 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 best
Top 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
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
1500 · seed 4242
- map
- Procedural Map
- size
- 1500
- seed
- 4242
Server
srv.info()- address
- 185.186.143.156:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Oct 2026, 08:42 UTC
- hostname
- –
- first seen
- 14 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 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 60/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 99/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 33/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 113/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 344/350 |
Quick answers
From the figures on this page.
Population
How does zombie-test compare in the rankings?
Player hours over seven days put zombie-test at #15,268, in the top 68% of the ranked set.
How full does zombie-test run?
The sample now reads 0 players for zombie-test, out of 10 slots. Over the last seven days it averaged 0 players.
Server data
What does performance look like on zombie-test?
The 48-hour average is 219 server fps, with a low of 192. Buildings, deployables and all else in the world took the count as high as 7,601 entities. The memory field tops out at 2,270 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does zombie-test run?
Rust network protocol 2634 and build 167781 on Linux is what zombie-test runs. The protocol has to match before you can join, and Steam does the updating.
Is zombie-test up, and what does its uptime show?
Online is the state at the latest refresh for zombie-test. The uptime it reports puts the last restart about 4 days 17 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 14 October 2026.
Where does zombie-test sit?
For zombie-test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 185.186.143.156:28015.
Settings and map
Which settings and rules does zombie-test run?
The name zombie-test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on zombie-test?
Size 1,500, seed 4242: the procedural map on zombie-test, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does zombie-test wipe, and on what schedule?
Too few wipes are on record for zombie-test to reveal its rhythm. 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 15 days 12 hours ago.
Lists and tags
Which Rust Data filters and lists contain zombie-test?
The Rust Data lists that zombie-test fits are: Modded Rust servers and Rust servers named for the undead. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on zombie-test hold?
Read by the game's server browser, the tags zombie-test publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into zombie-test?
In Rust, F1 opens the console: type client.connect 185.186.143.156:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.