Rust Data LabData lab · live
Live readings Servers11,695 Players53,611 Populated3,212 Fresh wipes · 3h137 Sampled every 5 min

Element card · group Modded · atomic number 15,338, its rank

Lexxer Map_test

Online 147.93.160.205:28815 checked 9m ago

moddedoxidepremium
Join the experiment
Atomic mass · players now 0/ 50 0% full Room to join
7-day average0peak –
Rank · atomic number#15,338top 69%
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0123410:0019:0004:0013:0023:0008:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
02040608010:0019:0004:0013:0023:0008:00

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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

too few wipes seen yet

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

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 07:04 UTC27d ago 0 – 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
  1. 1 Sh ShockRust | Bl… 132
    ShockRust | Blue | NoLimit no group limit · 149 on average 132/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 127
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 127/ 100
  3. 3 Re RETRO RUST #1 … 187
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average 187/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 75
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average 75/ 700
  5. 5 Ru RustSpain.com … 10
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average 10/ 200
  6. 6 Ru 404 RUST 2Х|ДЛ… 22
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 22/ 1,000

Quick answers

from the figures on this page

Server setup

What map is in play on Lexxer Map_test?

Lexxer Map_test runs a procedural map of size 4,250 with seed 1337; the game generates it. You can view it on RustMaps from this page, since matching size and seed produce the same map. Its map carries the name: Custom Map.

What rules has Lexxer Map_test set, and what settings are in force?

No gather rate appears in the name of Lexxer Map_test. With no change from the default, groups can hold up to 8 players. survival is the game mode, raiding, building and gathering: the standard game. Fighting and raiding between players are allowed. In the server browser it sits under Modded: the game is changed by plugins or settings. Oxide plugins are running on it. Joining requires Rust's premium status. Anti-cheat is on: Valve's VAC.

About the server

What region hosts Lexxer Map_test?

Nothing about a region is published by Lexxer Map_test. Rust Data Lab shows a server's stated location, not a verified position of the machine. Connect at 147.93.160.205:28815.

On what Rust version does Lexxer Map_test operate?

Rust network protocol 2635 and build 168909 on Windows is what Lexxer Map_test uses. Your game needs to match the protocol to join, and Steam updates it automatically.

How dependable is Lexxer Map_test for staying online?

Right now, Lexxer Map_test is reachable. About 6 days 13 hours ago is when it last restarted, based on its uptime. It was online for 167 of 168 hours in the last 7 full days, which is 99% uptime. It first appeared to Rust Data Lab on 13 September 2026.

Is Lexxer Map_test known for smooth running?

The last 48 hours show an average of 45 server fps and a minimum of 10. Buildings, deployables and everything else in the world added up to as many as 68,040 entities. Up to 3,739 MB of memory was used. Players feel lag when fps is low and the entity count climbs.

Wipe schedule

What is the wiping pattern on Lexxer Map_test?

The record holds too few of Lexxer Map_test's wipes to show its rhythm. The next monthly force wipe, which wipes all Rust servers, is scheduled for Thursday 5 November at 19:00 UTC. The world it is running now dates from 27 days 2 hours ago.

What does a typical wipe day on Lexxer Map_test involve?

Recent wipes on average reached 0 players at their busiest. The latest wipe's peak fell 0 hours after it began.

Lists and tags

What should you understand from the tags Lexxer Map_test carries?

These are the tags Lexxer Map_test makes public for the server browser to read: gmrust (Game mode): Standard Rust survival is the game here; mp50 (Max players): It has 50 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): Protocol 2635 is required; join only if your game matches it; cs168909 (Build): It runs build 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): A region code has not been set here; ^q (Premium): Joining requires Rust's premium status; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it lists under Modded. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Which Rust Data Lab filters and lists does Lexxer Map_test appear in?

These themed Rust Data Lab lists carry Lexxer Map_test: Modded Rust servers, measured. You can find it on the server list by applying these filters: Type: Modded; Game mode: Premium; Server tag: Premium ^q, Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

How does Lexxer Map_test compare with other servers in the rankings?

Player hours over the last week put Lexxer Map_test at #15,338, inside the top 69% of ranked servers.

How full is Lexxer Map_test right now?

Of 50 slots, 0 are taken on Lexxer Map_test right now. The seven-day average for this server is 0 players.

Connection

What steps get you onto Lexxer Map_test?

In Rust, press F1 and enter client.connect 147.93.160.205:28815. Or click Launch Rust here to open Rust via Steam and connect automatically. Joining requires Rust's premium status.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,^q,ts8,^o^z

Game

gmrust
Game mode Standard Rust survival is the game here.
mp50
Max players It has 50 slots.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol Protocol 2635 is required; join only if your game matches it.
cs168909
Build It runs build 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code A region code has not been set here.

Mods and access

^q
Premium Joining requires Rust's premium status.
^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it lists under Modded.

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.