Offline 86.106.182.68:28115 checked 27d ago
callbench
Connect
srv = rust.server("86.106.182.68:28117")
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 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 9h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 9h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 9h | 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, 21:52 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
- 86.106.182.68:28115
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 21:52 UTC
- hostname
- –
- first seen
- 30 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 | 115/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 184/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 57/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 | 24/1000 |
Quick answers
From the figures on this page.
Population
What position does callbench take in the server rankings?
Rank #15,938 on seven-day player hours for callbench, within the top 69% of all ranked servers.
What population does callbench carry?
The current row shows callbench offline; the last response was 27 days 7 hours ago.
Server facts
What Rust version does callbench run?
Rust network protocol 2634 and build 166494 on Windows is what callbench runs. Steam updates your game for you, but the protocol must match to join.
Is callbench up, and what does its uptime show?
Offline now for callbench, last seen 27 days 7 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 30 September 2026.
Which location does callbench run from?
There is no region published for callbench. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 86.106.182.68:28115 is its address.
Settings and map
What rules and settings are recorded for callbench?
You will not find a gather rate in the string callbench. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has callbench loaded?
The game generates its map: procedural, on callbench.
Wipe schedule
When does callbench wipe, and how often?
The only wipe callbench takes is the monthly force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 27 days 11 hours ago.
On callbench, what happens on wipe day?
Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which Rust Data filters and lists contain callbench?
On Rust Data, callbench 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.
Which meanings do the tags on callbench hold?
The game's server browser reads these tags from callbench: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166494 (Build): Recorded game build: 166494; 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.
Connecting
What is the way into callbench?
Enter client.connect 86.106.182.68:28115 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.