Offline 203.16.163.26:29038 checked 19d ago
FATE RUST test
Connect
srv = rust.server("203.16.163.26:29039")
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 bestTop 72% 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 | Fri 2 Oct, 14:05 UTC27d ago | 0 | NaN | running | 0 |
# 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
1000 · seed 50000
- map
- Procedural Map
- size
- 1000
- seed
- 50000
Server
srv.info()- address
- 203.16.163.26:29038
- region
- –
- max players
- 75
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 14:05 UTC
- hostname
- –
- first seen
- 16 Sep 2026
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 · 150 on average | 54/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 95/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 | 99/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 336/350 |
Quick answers
From the figures on this page.
Player counts
How does FATE RUST test compare in the rankings?
Rank #15,817 on seven-day player hours for FATE RUST test, within the top 72% of all ranked servers.
What population does FATE RUST test carry?
Offline now for FATE RUST test, with the last sample 19 days 13 hours ago.
Server data
Which Rust version is FATE RUST test on?
Rust network protocol 2634 and build 166586 on Linux is what FATE RUST test runs. Joining needs the same protocol on your game; Steam handles the update.
Is FATE RUST test up, and what does its uptime show?
FATE RUST test is offline at this refresh; the last response came 19 days 13 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 16 September 2026.
Which location does FATE RUST test run from?
No region is published by FATE RUST test. Rust Data does not look up where the machine stands; it shows where a server says it is. 203.16.163.26:29038 is its address.
Rules, settings, map
Which rules apply on FATE RUST test, and what settings?
The name FATE RUST test carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is not running; Valve's anti-cheat is off.
What is the map on FATE RUST test?
Size 1,000, seed 50000: the procedural map on FATE RUST test, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does FATE RUST test wipe, and on what schedule?
A rhythm cannot be read from the wipes of FATE RUST test on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 27 days 7 hours ago.
On FATE RUST 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.
Tags and filters
Which lists on Rust Data hold FATE RUST test, and which filters?
The Rust Data lists that FATE RUST test fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on FATE RUST test?
The game's server browser reads these tags from FATE RUST test: gmrust (Game mode): Rust survival in its standard form; mp75 (Max players): Slot count: 75; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166586 (Build): The server runs build 166586; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^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.
How to join
How can I connect to FATE RUST test?
Enter client.connect 203.16.163.26:29038 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.