Offline 141.145.202.158:28015 checked 41d ago
box64-benchmark
Connect
srv = rust.server("141.145.202.158: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
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
- 141.145.202.158:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 17 Sep 2026, 02:31 UTC
- hostname
- –
- first seen
- 17 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 · 155 on average | 34/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 34/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 31/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 4/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does box64-benchmark rank?
Player hours over seven days put box64-benchmark at #15,523, in the top – of the ranked set.
What population does box64-benchmark carry?
The current row shows box64-benchmark offline; the last response was 41 days 22 hours ago.
Server facts
What is the Rust version on box64-benchmark?
The build is Rust network protocol 2633 and build 163794 on Linux, run by box64-benchmark. Steam updates your game for you, but the protocol must match to join.
How reliable is box64-benchmark, and is it up?
The latest sample has box64-benchmark offline, with a last sighting 41 days 22 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 17 September 2026.
In which location is box64-benchmark hosted?
No region is published by box64-benchmark. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 141.145.202.158:28015.
Settings and map
Which settings and rules does box64-benchmark run?
The name box64-benchmark carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on box64-benchmark?
box64-benchmark runs a procedural map, which the game generates.
Wipe data
When does box64-benchmark wipe, and on what schedule?
A rhythm cannot be read from the wipes of box64-benchmark on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 41 days 22 hours ago.
Lists and tags
Which Rust Data filters and lists contain box64-benchmark?
On Rust Data, box64-benchmark appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on box64-benchmark?
The game's server browser reads these tags from box64-benchmark: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): Recorded game build: 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join box64-benchmark?
Enter client.connect 141.145.202.158:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.