Rust Data

rustdata.spaceservers147.93.160.205:28816.ipynb

Run all rust-data · live

‹ All servers

Online 147.93.160.205:28815 checked 10m ago

Lexxer Map_test

moddedoxidepremium

Connect

srv = rust.server("147.93.160.205:28816")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,349 # top 69%
last wipe 26d ago # no schedule published
next wipe – # too few wipes seen yet
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123402:0011:0020:0005:0014:0000:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608002:0011:0020:0005:0014:0000: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 07:04 UTC26d ago 0 NaN 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.

display(srv.map, srv.info())

Map

4250 · seed 1337
Map of Lexxer Map_test
map
Custom Map
size
4250
seed
1337

Server

srv.info()
address
147.93.160.205:28815
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 07:04 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
Herzlich willkommen, dieser Server ist ausschließlich für das kontrollieren erstellter Maps und Prefabs gedacht.

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 155 on average34/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average135/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average34/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average28/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average4/1000

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does Lexxer Map_test rank?

Player hours over seven days put Lexxer Map_test at #15,349, in the top 69% of the ranked set.

How full does Lexxer Map_test run?

Current row: 0 players on Lexxer Map_test, against 50 slots. Over the last seven days it averaged 0 players.

Server data

What does performance look like on Lexxer Map_test?

The 48-hour average is 48 server fps, with a low of 10. Entity numbers reached 68,006, and that includes buildings, deployables and the rest. The memory field tops out at 3,584 MB. Low fps plus an entity count on the way up is the lag players report.

Which Rust version is Lexxer Map_test on?

Version Rust network protocol 2635 and build 168909 on Windows is reported by Lexxer Map_test. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Lexxer Map_test, and is it online now?

Online is the state at the latest refresh for Lexxer Map_test. The uptime it reports puts the last restart about 6 days 5 hours ago. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 13 September 2026.

Where does Lexxer Map_test sit?

For Lexxer Map_test, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 147.93.160.205:28815.

Map and rules

Which settings and rules does Lexxer Map_test run?

The name Lexxer Map_test carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Premium status is needed to join. Anti-cheat status: VAC on.

Which map has Lexxer Map_test selected?

Size 4,250, seed 1337: the procedural map on Lexxer Map_test, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Recorded under map name: Custom Map.

Wipe schedule

On what schedule does Lexxer Map_test wipe?

The record for Lexxer Map_test holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 26 days 18 hours ago.

What is wipe day on Lexxer Map_test like?

Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.

Lists and tags

Which lists on Rust Data hold Lexxer Map_test, and which filters?

These Rust Data lists include Lexxer Map_test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Game mode: Premium; Server tag: Premium ^q, Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on Lexxer Map_test?

Read by the game's server browser, the tags Lexxer Map_test publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^q (Premium): Premium status is needed to join; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into Lexxer Map_test?

In Rust, F1 opens the console: type client.connect 147.93.160.205:28815. Launch Rust on this page does the same by opening the game through Steam and connecting. Premium status is needed to join.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players The server lists 50 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^q
Premium Premium status is needed to join.
^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 43,056 players 11,700 servers online