Offline 64.40.8.7:28015 checked 1d ago
[TEST] Warden test server
Connect
srv = rust.server("64.40.8.7: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 17 Sep. 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 9% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()
Next wipe Thursday 29 October, 19:03 UTC, in 1d 14h. # Every Monday at 17:37 and every Thursday at 19:03 UTC · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 1d 14h | Thu 29 Oct, 19:03 UTC | wipe |
| 1 | 5d 13h | Mon 2 Nov, 17:37 UTC | wipe |
| 2 | 8d 14h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 3 | 12d 13h | Mon 9 Nov, 17:37 UTC | wipe |
| 4 | 15d 14h | Thu 12 Nov, 19:03 UTC | wipe |
| 5 | 19d 13h | Mon 16 Nov, 17:37 UTC | wipe |
| 6 | 22d 14h | Thu 19 Nov, 19:03 UTC | wipe |
| 7 | 26d 13h | Mon 23 Nov, 17:37 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 14, 8 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 17:37 UTC1d ago | NaN | NaN | running | 11 |
| 1 | Thu 22 Oct, 19:03 UTC5d ago | 14 | held half | 3.9 days | 1 |
| 2 | Mon 19 Oct, 19:03 UTC8d ago | 12 | held half | 3 days | 0 |
| 3 | Thu 15 Oct, 19:03 UTC12d ago | 6 | held half | 4 days | 0 |
| 4 | Mon 12 Oct, 19:03 UTC15d ago | 9 | held half | 3 days | 2 |
| 5 | Thu 8 Oct, 19:03 UTC19d ago | 9 | held half | 4 days | 3 |
| 6 | Mon 5 Oct, 19:03 UTC22d ago | 6 | held half | 3 days | 2 |
| 7 | Thu 1 Oct, 17:54 UTC FW26d ago | 12 | held half | 4 days | 10 |
| 8 | Mon 28 Sep, 19:03 UTC29d ago | 8 | held half | 3 days | 3 |
| 9 | Thu 24 Sep, 19:03 UTC33d ago | 5 | held half | 4 days | 0 |
| 10 | Mon 21 Sep, 19:02 UTC36d ago | 7 | held half | 3 days | 0 |
| 11 | Thu 17 Sep, 19:02 UTC40d ago | 12 | held half | 4 days | 4 |
| 12 | Mon 14 Sep, 19:03 UTC43d ago | 8 | held half | 3 days | 6 |
# 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
3500 · seed 1337
- map
- Procedural Map
- size
- 3500
- seed
- 1337
Server
srv.info()- address
- 64.40.8.7:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 17:37 UTC
- hostname
- us100x.icefuse.net
- first seen
- 13 Sep 2026
Operator · icefuse.net
rust.servers(operator="icefuse.net").sort_values("players")
30 servers publish a icefuse.net hostname; the busiest are listed.
About this server · in its own words
print(srv.description)
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 · 159 on average | 44/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 53/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 22/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 6/1000 |
Quick answers
From the figures on this page.
Population data
How does [TEST] Warden test server compare in the rankings?
Rank #2,072 on seven-day player hours for [TEST] Warden test server, within the top 9% of all ranked servers.
What population does [TEST] Warden test server carry?
[TEST] Warden test server returns no live count at this refresh, having last been seen 34 hours ago. Over the last seven days it averaged 4 players and peaked at 14.
Server data
Which Rust version is [TEST] Warden test server on?
Version Rust network protocol 2635 and build 168909 on Linux is reported by [TEST] Warden test server. Steam updates your game for you, but the protocol must match to join.
How reliable is [TEST] Warden test server, and is it online now?
The latest sample has [TEST] Warden test server offline, with a last sighting 34 hours ago. Over the last 7 full days the hours up number 92 of 168, 55%. Rust Data logged it first on 13 September 2026.
In which location is [TEST] Warden test server hosted?
No region is published by [TEST] Warden test server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 64.40.8.7:28015 is its address.
Map and rules
Which settings and rules does [TEST] Warden test server run?
The name [TEST] Warden test server carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. Anti-cheat status: VAC on.
Which map has [TEST] Warden test server loaded?
The game generates the map on [TEST] Warden test server: procedural, size 3,500, seed 1337. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does [TEST] Warden test server wipe, and on what schedule?
The wipe rhythm for [TEST] Warden test server is every Monday at 17:37 and every Thursday at 19:03 UTC. Thursday 29 October at 19:03 UTC is when the next wipe is due. The world it runs now was generated 34 hours ago.
What is wipe day on [TEST] Warden test server like?
Across recent wipes the busiest point averaged 11 players. The crowd on the latest wipe topped out 8 hours after it began. Half the peak or more was held to the next wipe in 100% of recent wipes.
Tags and filters
Which lists on Rust Data hold [TEST] Warden test server, and which filters?
On Rust Data, [TEST] Warden test server appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Who operates [TEST] Warden test server?
The same operator most likely runs [TEST] Warden test server and 29 other servers we track, as all publish a icefuse.net hostname.
Which meanings do the tags on [TEST] Warden test server hold?
The game's server browser reads these tags from [TEST] Warden test server: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join [TEST] Warden test server?
Enter client.connect 64.40.8.7:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://icefuse.com/.
