Rust StatisticsWorking papers on every public Rust server · 86,491 players now

lexazabivnoi228

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 42d ago · 178.214.247.41:28015

Abstract

We describe the public Rust server lexazabivnoi228, reached at 178.214.247.41:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #13,333 of all servers. It last wiped 42d ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/157% full
In the queue0no queue
Seven-day mean0peak –
Rank2#13,333no region published
Last wipe42d agono schedule published
Next wipe3–no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: 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.

4Rank

Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 4: The map: Procedural Map.
Table 3: The server's published settings.
Address178.214.247.41:28015
Region–
Max players15
Group limit8, the default
Wipe schedule–
Last wipe15 Sep 2026, 10:20 UTC
Hostname–
First seen15 Sep 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are community tab servers measured [2] and next Rust wipe times [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 504 on average762/825
Rustoria.co - EU MainEU · groups of 16+ · weekly · 345 on average51/250
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 340 on average110/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 314 on average414/500
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average237/300
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 259 on average181/300

Appendix AQuick answers

From the figures on this page.

Server details

A.1What is the location of lexazabivnoi228?

A region is not published by lexazabivnoi228. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 178.214.247.41:28015 is its address.

A.2What is the online status and reliability of lexazabivnoi228?

lexazabivnoi228 is currently offline, with the last sighting 42 days 9 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. It was first observed on 15 September 2026 by Rust Statistics.

A.3What is the Rust version for lexazabivnoi228?

The version of Rust on lexazabivnoi228 is network protocol 2633 and build 163794, and the operating system is Windows. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.4What schedule does lexazabivnoi228 follow for wipes?

There are not yet enough recorded wipes for lexazabivnoi228 to reveal its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 42 days 10 hours have passed since the current world was generated.

Population

A.5How does lexazabivnoi228 compare with other Rust servers in the rankings?

Ranked by player hours across seven days, lexazabivnoi228 holds #13,333, in the top – of all ranked servers.

A.6How would you characterise the player activity on lexazabivnoi228?

At this moment lexazabivnoi228 is offline, having last been seen 42 days 9 hours ago.

Tags and filters

A.7How should the tags on lexazabivnoi228 be interpreted?

The game's server browser reads gmrust (Game mode): This is survival as standard Rust plays; mp15 (Max players): It offers 15 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs163794 (Build): Build 163794 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set, which lexazabivnoi228 publishes as its tags. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.8Where can lexazabivnoi228 be found among the Rust Statistics lists and filters?

Rust community servers, measured are the Rust Statistics lists that lexazabivnoi228 fits. It appears under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Rules, settings, map

A.9Which settings and rules are in force on lexazabivnoi228?

Its name carries no gather rate for lexazabivnoi228. At 8 players, the group limit equals the game's default. The mode is survival, which means gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. Community is its category in the server browser. VAC is active: that is Valve's anti-cheat.

A.10On which map does lexazabivnoi228 take place?

A procedural map, generated by the game, is what lexazabivnoi228 runs.

How to join

A.11What is the process for joining lexazabivnoi228?

Enter client.connect 178.214.247.41:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp15,ptrak,$r?,v2633,gmrust,cs163794,ts8.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp15Max players. It offers 15 slots.
ts8Group limit. 8 per team, the value the game sets by default.
v2633Protocol. The game protocol is 2633; your client must match it to join.
cs163794Build. Build 163794 is the one running.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. No region code is set.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Community tab servers measured. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.