Offline 79.127.184.138:28015 checked 40d ago
WightForgeRust
Connect
srv = rust.server("79.127.184.138: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 bestWipe 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 18 Sep, 17:36 UTC40d ago | 0 | NaN | running | 0 |
| 1 | Fri 18 Sep, 02:00 UTC41d ago | 0 | NaN | 0.6 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
- 79.127.184.138:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Sep 2026, 17:36 UTC
- hostname
- –
- first seen
- 16 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 · 149 on average | 167/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 · 118 on average | 182/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 70/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 13/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 20/1000 |
Quick answers
From the figures on this page.
Player counts
How does WightForgeRust compare in the rankings?
Player hours over seven days put WightForgeRust at #15,444, in the top – of the ranked set.
What population does WightForgeRust carry?
WightForgeRust returns no live count at this refresh, having last been seen 40 days 14 hours ago.
Server facts
What Rust version does WightForgeRust run?
Rust network protocol 2633 and build 164530 on Linux is what WightForgeRust runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is WightForgeRust, and is it up?
WightForgeRust is offline at this refresh; the last response came 40 days 14 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 16 September 2026.
Which location does WightForgeRust run from?
No region is published by WightForgeRust. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 79.127.184.138:28015 is its address.
Map and rules
Which rules apply on WightForgeRust, and what settings?
The name WightForgeRust carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC off.
Which map has WightForgeRust loaded?
The game generates its map: procedural, on WightForgeRust.
Wipe schedule
When does WightForgeRust wipe, and on what schedule?
The record for WightForgeRust holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 40 days 18 hours ago, and that is the one in play.
On WightForgeRust, what happens on wipe day?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Where does WightForgeRust appear among Rust Data lists and filters?
The Rust Data lists that WightForgeRust 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 WightForgeRust?
The game's server browser reads these tags from WightForgeRust: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs164530 (Build): The server runs build 164530; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to WightForgeRust?
Enter client.connect 79.127.184.138:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.