Offline 84.134.57.199:28015 checked 10d ago
Forkes Testserver
Connect
srv = rust.server("84.134.57.199:28016")
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 60% 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 14 Oct, 11:07 UTC14d ago | 1 | NaN | running | 0 |
| 1 | Tue 13 Oct, 15:24 UTC15d ago | 1 | NaN | 0.8 days | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 84.134.57.199:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Oct 2026, 11:52 UTC
- hostname
- –
- first seen
- 13 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 · 152 on average | 38/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 62/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 14/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Forkes Testserver take in the server rankings?
Rank #13,065 on seven-day player hours for Forkes Testserver, within the top 60% of all ranked servers.
How many players does Forkes Testserver hold at once?
Forkes Testserver returns no live count at this refresh, having last been seen 10 days 19 hours ago.
Server facts
Which Rust version is Forkes Testserver on?
Rust network protocol 2634 and build 167781 on Windows is what Forkes Testserver runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Forkes Testserver, and is it up?
Forkes Testserver is offline at this refresh; the last response came 10 days 19 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 13 October 2026.
In which location is Forkes Testserver hosted?
There is no region published for Forkes Testserver. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 84.134.57.199:28015 is its address.
Settings and map
Which settings and rules does Forkes Testserver run?
The name Forkes Testserver 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. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Forkes Testserver loaded?
A procedural map runs on Forkes Testserver, generated by the game.
Wipe schedule
When does Forkes Testserver wipe, and on what schedule?
Too few wipes are on record for Forkes Testserver to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 14 days 17 hours ago, and that is the one in play.
What is wipe day on Forkes Testserver like?
Recent wipes averaged 1 players at their peak. 1 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which lists on Rust Data hold Forkes Testserver, and which filters?
The Rust Data lists that Forkes Testserver fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Forkes Testserver?
The game's server browser reads these tags from Forkes Testserver: gmvanilla (Game mode): Game mode: vanilla survival; mp2 (Max players): Slot count: 2; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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 Forkes Testserver?
In Rust, F1 opens the console: type client.connect 84.134.57.199:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.