Offline 149.33.15.199:28015 checked 5d ago
RustRearm private workbench capture
Connect
srv = rust.server("149.33.15.199: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 bestTop 58% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 149.33.15.199:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 21 Oct 2026, 20:28 UTC
- hostname
- –
- first seen
- 22 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 553 on average | 323/375 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 201/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 294 on average | 36/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 293 on average | 26/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 273 on average | 56/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 252 on average | 72/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does RustRearm private workbench capture rank?
Over the last seven days RustRearm private workbench capture sits at #12,938 on player hours, in the top 58% of ranked servers.
How full does RustRearm private workbench capture run?
Offline now for RustRearm private workbench capture, with the last sample 5 days 22 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server facts
Which Rust version is RustRearm private workbench capture on?
The build is Rust network protocol 2635 and build 168931 on Linux, run by RustRearm private workbench capture. Steam updates your game for you, but the protocol must match to join.
Is RustRearm private workbench capture up, and what does its uptime show?
Offline now for RustRearm private workbench capture, last seen 5 days 22 hours ago. Uptime of 1% across the last 5 full days: 1 hours of 120. Its earliest recorded date in Rust Data is 22 October 2026.
Which location does RustRearm private workbench capture run from?
There is no region published for RustRearm private workbench capture. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 149.33.15.199:28015.
Rules, settings, map
Which rules apply on RustRearm private workbench capture, and what settings?
No gather rate appears in the name: RustRearm private workbench capture. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. VAC is not running; Valve's anti-cheat is off.
Which map has RustRearm private workbench capture loaded?
A procedural map runs on RustRearm private workbench capture, generated by the game.
Wipe data
When does RustRearm private workbench capture wipe, and on what schedule?
The record for RustRearm private workbench capture holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 7 days 3 hours ago, and that is the one in play.
Tags and filters
Where does RustRearm private workbench capture appear among Rust Data lists and filters?
On Rust Data, RustRearm private workbench capture appears in these lists: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on RustRearm private workbench capture hold?
The game's server browser reads these tags from RustRearm private workbench capture: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): Slot count: 4; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168931 (Build): Recorded game build: 168931; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. 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 RustRearm private workbench capture?
Enter client.connect 149.33.15.199:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.