RustVideoBot private capture
Online 109.235.247.237:28115 checked 14m ago
Server instruments
last reading Thu 21:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 61 · below 20 is lag, below 10 is badEntities
48 h range 45,272–47,672 · memory 3,020 MBUptime
9 days 6 hours since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 2 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 60% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot 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 1, 2 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 16:59 UTC27d ago | 1 | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 39/500
- 132/100
- 86/225
- 32/700
- 86/700
- 309/350
Quick answers
from the figures on this pageWipe timing
What happens on RustVideoBot private capture when wipe day comes?
The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 2 hours in.
What wipe timing does RustVideoBot private capture follow?
Its rhythm cannot be told from the wipes of RustVideoBot private capture on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 27 days 5 hours ago.
Tag meanings
How should you read the tags on RustVideoBot private capture?
These are the tags RustVideoBot private capture publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166655 (Build): Game build reading: 166655; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show RustVideoBot private capture?
On Rust Metrics, RustVideoBot private capture sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Occupancy
What position does RustVideoBot private capture hold among Rust servers?
Ranking for RustVideoBot private capture: #13,461 on seven-day player hours, top 60% of all ranked servers.
What is the population on RustVideoBot private capture?
0 of 2 slots are filled on RustVideoBot private capture right now. Seven-day check: 0 players on average. Peak reading: 1. Average at the busiest hour was 0 players, at 10:00 UTC over the last 48 hours.
Server
What location is RustVideoBot private capture hosted in?
Reading: location. RustVideoBot private capture gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 109.235.247.237:28115.
What Rust version is RustVideoBot private capture on?
Reading: RustVideoBot private capture, Rust network protocol 2634 and build 166655, Windows. Matching protocol is required to join. Let Steam update your game.
What is the performance reading for RustVideoBot private capture?
Check: fps. Average 182 server fps over the last 48 hours, low of 61. Within range. Reading: 47,672 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 3,459 MB. What players call lag comes from low fps and an entity count on the rise.
How reliable is RustVideoBot private capture, and is it online now?
Reading: online. RustVideoBot private capture answers right now. By its reported uptime, the last restart was roughly 9 days 6 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 2 October 2026, recorded by Rust Metrics.
Map and rules
What rules does RustVideoBot private capture enforce, and what are its settings?
Reading the name gives no gather rate for RustVideoBot private capture. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. VAC is off. That is Valve's anti-cheat.
What map is RustVideoBot private capture on?
From seed 424242, the game generates the procedural map on RustVideoBot private capture. Its size is 3,000. View it on RustMaps from this page: matching size and seed give an identical map.
How to join
How can you get onto RustVideoBot private capture?
Press F1 in Rust and enter client.connect 109.235.247.237:28115. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.