Offline 200.84.61.132:28015 checked 22d ago
RUSTINGEZ
Connect
srv = rust.server("200.84.61.132: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 7 Oct. 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 71% 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 6d 23h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 23h | 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 | Wed 7 Oct, 14:14 UTC22d 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())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 317 on average | 394/475 |
| 1 | eulongtest (private perf box) | EU · groups of 14+ · monthly · 267 on average | 480/8 |
| 2 | Rusty Moose |EU Monthly| | EU · groups of 12+ · monthly · 212 on average | 272/300 |
| 3 | [EU East] Facepunch 4 | EU · groups of 8+ · monthly · 162 on average | 135/350 |
| 4 | [EU] Facepunch 1 | EU · groups of 8+ · monthly · 160 on average | 191/400 |
| 5 | Rustopia.gg - US Large | NA · groups of 16+ · monthly · 126 on average | 88/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does RUSTINGEZ rank?
Rank #15,901 on seven-day player hours for RUSTINGEZ, within the top 71% of all ranked servers.
How many players does RUSTINGEZ hold at once?
Offline now for RUSTINGEZ, with the last sample 22 days 2 hours ago.
Server data
What Rust version does RUSTINGEZ run?
Version Rust network protocol 2634 and build 167103 on Windows is reported by RUSTINGEZ. The protocol has to match before you can join, and Steam does the updating.
Is RUSTINGEZ up, and what does its uptime show?
RUSTINGEZ is offline at this refresh; the last response came 22 days 2 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 7 October 2026.
Which location does RUSTINGEZ run from?
There is no region published for RUSTINGEZ. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 200.84.61.132:28015.
Rules, settings, map
What rules and settings are recorded for RUSTINGEZ?
The name RUSTINGEZ carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. The server browser lists it under Community. Its own label is vanilla: untouched settings: rates, kits and rules as shipped. Joining requires Rust's premium status. Anti-cheat status: VAC on.
Which map has RUSTINGEZ loaded?
Size 4,500, seed 1337: the procedural map on RUSTINGEZ, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: Custom Map.
Wipes and dates
When does RUSTINGEZ wipe, and on what schedule?
A single wipe each month, the force wipe, is all RUSTINGEZ does. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 22 days 3 hours ago, and that is the one in play. Its tags carry a monthly wipe schedule.
On RUSTINGEZ, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Where does RUSTINGEZ appear among Rust Data lists and filters?
The Rust Data lists that RUSTINGEZ fits are: Rust community servers, unfiltered and Vanilla Rust servers. These filters bring it up on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Game mode: Premium; Server tag: Monthly ^m, Vanilla ^v and Premium ^q; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on RUSTINGEZ?
The game's server browser reads these tags from RUSTINGEZ: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167103 (Build): The server runs build 167103; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^q (Premium): Joining requires Rust's premium status. 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.
Join steps
What is the way to join RUSTINGEZ?
In Rust, F1 opens the console: type client.connect 200.84.61.132:28015. Launch Rust on this page does the same by opening the game through Steam and connecting. Joining requires Rust's premium status.