Online 76.18.83.131:28015 checked 12m ago
RFC's Test Server
Connect
srv = rust.server("76.18.83.131: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. 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 15h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 15h | Thu 3 Dec, 19:00 UTC | FW 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 | Thu 1 Oct, 19:54 UTC FW27d 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 76.18.83.131:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 19:54 UTC
- hostname
- –
- first seen
- 15 Sep 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 · 154 on average | 31/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 · 117 on average | 42/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 11/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 1/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does RFC's Test Server rank?
Rank #15,358 on seven-day player hours for RFC's Test Server, within the top 69% of all ranked servers.
How many players does RFC's Test Server hold at once?
The sample now reads 0 players for RFC's Test Server, out of 2 slots. Over the last seven days it averaged 0 players.
Server data
What is the Rust version on RFC's Test Server?
Version Rust network protocol 2635 and build 168909 on Linux is reported by RFC's Test Server. Steam updates your game for you, but the protocol must match to join.
How reliable is RFC's Test Server, and is it up?
The current sample puts RFC's Test Server online. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 15 September 2026.
Which location does RFC's Test Server run from?
No region is published by RFC's Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. 76.18.83.131:28015 is its address.
Map and rules
What rules and settings are recorded for RFC's Test Server?
The name RFC's Test Server carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, 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. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has RFC's Test Server selected?
The game generates its map: procedural, on RFC's Test Server.
Wipes and dates
When does RFC's Test Server wipe, and how often?
The only wipe RFC's Test Server takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 27 days 8 hours ago, and that is the one in play.
What is wipe day on RFC's Test Server like?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which Rust Data filters and lists contain RFC's Test Server?
On Rust Data, RFC's 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 Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on RFC's Test Server hold?
The game's server browser reads these tags from RFC's Test Server: gmvanilla (Game mode): Game mode: vanilla survival; mp2 (Max players): Slot count: 2; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 RFC's Test Server?
Enter client.connect 76.18.83.131:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.