lex
Offline 5.77.2.238:28015 checked 38d 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
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.
Settings and map
What settings and rules does lex run?
You will find no gather rate in the name of lex. The default group limit of 8 players applies. The server runs survival, building, gathering and raiding in the standard game. Fighting and raiding other players is permitted. The server browser lists it under Community; it is a community server. The server has VAC, Valve's anti-cheat, turned on.
What is the map on lex?
lex runs a procedural map, which the game generates.
Tags and filters
Which lists and filters on Rust Server Index is lex filed under?
These lists on Rust Server Index take lex: Community Rust servers, indexed. These filters on the server list bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What is meant by the tags on lex?
These are the tags lex publishes; the game's server browser reads this list: gmrust (Game mode): Rust survival, as standard; mp500 (Max players): The queue ceiling sits at 500; ts8 (Group limit): Game default applies: teams of up to 8; v2633 (Protocol): Your client must run protocol 2633 to connect; cs164530 (Build): It runs build 164530; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): A region code is absent. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe dates
Which wipe timetable does lex follow?
The record holds too few of lex's wipes to tell its rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. Its present world dates from 38 days 17 hours.
Player counts
Where does lex sit in the rankings?
On player hours over seven days, lex takes #15,467, within the top – of ranked servers.
What does the player count on lex look like?
Filed under offline: lex, last seen 38 days 15 hours ago.
Server facts
What version does lex use?
Rust network protocol 2633 and build 164530 on Windows is what you will find on lex. To join you need the same protocol; Steam handles the update.
What is the uptime and current status of lex?
As of now lex is offline, with its last appearance 38 days 15 hours ago. Of the last 7 full days, 0 of 168 hours were up, 0% of the time. On 20 September 2026 it was first seen by Rust Server Index.
What is the location of lex?
There is no region on record for lex; it publishes none. Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 5.77.2.238:28015.
How to join
What is the way onto lex?
Two ways in. Type client.connect 5.77.2.238:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp500,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp500
ts8
v2633
cs164530
ptrak
$r?
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.