Ingibitor2
Offline 85.172.77.93:28015 checked 25d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
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| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 205/500
- 121/100
- 183/225
- 126/700
- 19/200
- 50/1000
Quick answers
from the figures on this pageWipe timing
What wipe timing does Ingibitor2 follow?
Its rhythm cannot be told from the wipes of Ingibitor2 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. 25 days 2 hours ago the current world was made.
Tags
How should you read the tags on Ingibitor2?
These are the tags Ingibitor2 publishes, and the server browser reads them: mp10 (Max players): Slots: 10; v2150 (Protocol): Match the game version: protocol 2150 is required; oxide (Oxide): Check: framework. Oxide (uMod) handles plugins; modded (Modded): Modded: plugins or settings depart from the stock game; h1791deb9 (Custom tag): A plugin or the owner set this tag; Rust does not ship it; stok (Custom tag): A plugin or the owner set this tag; Rust does not ship it. 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 Ingibitor2?
These Rust Metrics lists carry Ingibitor2: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded.
Occupancy
Where does Ingibitor2 sit in the rankings?
Ranking for Ingibitor2: #16,020 on seven-day player hours, top 71% of all ranked servers.
How full does Ingibitor2 get?
Status for Ingibitor2: offline. Last seen 25 days 1 hours ago.
Operator and location
Where does Ingibitor2 sit?
No region tag on Ingibitor2. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 85.172.77.93:28015.
What Rust version is Ingibitor2 on?
Version check: Rust network protocol 2150 on Windows, run by Ingibitor2. Matching protocol is required to join. Let Steam update your game.
What is the uptime on Ingibitor2, and is it online?
Ingibitor2 reports offline. The last reading came 25 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 3 October 2026.
Settings and map
How is Ingibitor2 configured, and what rules are in force?
Check: gather rate. The name Ingibitor2 does not state one. No group limit is published. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. VAC is on. That is Valve's anti-cheat.
What map is Ingibitor2 on?
Check: map. Procedural, generated by the game, on Ingibitor2.
How to join
How can you get onto Ingibitor2?
Check: join. Open Rust, press F1, then enter client.connect 85.172.77.93:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.