RS-13183Community server
lexazabivnoi228
Offline 77.79.177.182:28015 checked 21d ago
Players
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
Top 57% 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
| 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.
Quick answers
From the figures on this page.
Player activity
How many players are usually on lexazabivnoi228?
lexazabivnoi228 is offline at this moment; the last signal was 21 days 10 hours ago.
Where does lexazabivnoi228 sit in the rankings?
On player hours across seven days, lexazabivnoi228 is #13,183, inside the top 57% of all ranked servers.
Server tags and lists
Where does lexazabivnoi228 show up in Top Rust Servers lists and filters?
On these Top Rust Servers lists you will find lexazabivnoi228: Best Rust community servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What is the meaning of the tags on lexazabivnoi228?
The game's server browser reads the tags that lexazabivnoi228 publishes: gmrust (Game mode): Survival follows the standard Rust ruleset; mp15 (Max players): There are 15 slots; ts8 (Group limit): The team limit is 8, which is the game default; v2633 (Protocol): This server runs protocol 2633; match it to connect; cs165217 (Build): Running game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code not set. At the top of this page you also see its players now, its queue, and the time its world was made, taken from the tags.
Settings and map
What map is used on lexazabivnoi228?
A procedural map, created by the game, is in use on lexazabivnoi228.
What does lexazabivnoi228 run for rules and settings?
You will not find a gather rate in the name lexazabivnoi228. Up to 8 players per group, as the game defaults. You play survival, the normal mode where you gather, build and raid. You can fight and raid other players. The server browser shows it under Community. VAC, Valve's anti-cheat, is enabled.
Server details
What Rust version is lexazabivnoi228 on?
Rust network protocol 2633 and build 165217 is what lexazabivnoi228 runs, on Windows. Joining requires matching protocols, and Steam updates your game automatically.
What is the server location for lexazabivnoi228?
No region is published by lexazabivnoi228. What Top Rust Servers shows is where a server says it is, not where the machine stands, which it does not look up. 77.79.177.182:28015 is its address.
Is lexazabivnoi228 currently online?
The server lexazabivnoi228 is down at the moment, with its last appearance 21 days 10 hours ago. It spent 0 of the last 168 hours online across 7 days, giving 0% uptime. Its first appearance in Top Rust Servers was on 22 September 2026.
Wipe details
How often does lexazabivnoi228 wipe?
Not enough wipe data exists yet to identify the rhythm of lexazabivnoi228. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. The world it is running now dates from 28 days 17 hours ago.
Joining the server
What are the steps to join lexazabivnoi228?
To connect manually, open the console with F1 and type client.connect 77.79.177.182:28015. Or click Launch Rust on this page to open Rust through Steam and connect directly.