RUST METRICSFlight deck · live data
Data live Servers11,789 Players63,543 Populated3,532 Fresh wipes 3 h121 Scan5 min
‹ All servers192.121.44.42:28016
Online Full Queue Fresh wipe Wipe due No query

[EU/SWE] Playstar - SOLO - LARGE MAP

Online EU 192.121.44.42:28016 checked 13m ago

biweekly wipes vanillaoxidepremium
COM 1 · connect

Server instruments

last reading Wed 20:00 UTC
0 12 25 38 50 PAX 10 /50

Players now

20% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 55 SERVER FPS

Server fps

48 h low 47 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 188,079 ×1000

Entities

48 h range 180,346–190,789 · memory 4,560 MB
1239 ET SINCE RESTART 17:25

Uptime

17 h 25 min since its last restart, at the last reading
7-day average10peak 24
Rank#967top 4% · #417 in EU
Last wipe13d agobiweekly schedule
Next wipe7d 20hThu 5 Nov, 19:00 UTC FW
Memory4,560MB48 h peak 13 players
REC 1

Players

AveragePeak
0510152023:0008:0017:0001:0010:0020:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608023:0008:0017:0001:0010:0020: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15001k1.5k2k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 4% of all ranked servers, top 14% in EU. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

fixed weekdays

Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. The force wipe · high confidence

usual gap28 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak32players, last three wipes
crowd held0%else halves by day 9

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 20hFW
  2. WPT 2Thu 12 Nov, 16:39 UTC14d 18h
  3. WPT 3Thu 3 Dec, 19:00 UTC35d 20hFW
  4. WPT 4Thu 10 Dec, 16:39 UTC42d 18h

The first 48 hours of its last wipes

Thu 15 OctThu 1 OctThu 17 Sep
010203040+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 16:39 UTC13d ago 34 – running 5
Thu 1 Oct, 18:45 UTC FW27d ago 33 halved by day 8 13.9 days 5
Thu 17 Sep, 16:55 UTC41d ago 28 halved by day 10 14.1 days 2

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on [EU/SWE] Playstar - SOLO - LARGE MAP when wipe day comes?

At their busiest, its recent wipes drew 32 players on average. 28 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. When it didn't hold, by day 9 it fell below half.

What wipe timing does [EU/SWE] Playstar - SOLO - LARGE MAP follow?

every 4 weeks on Thursday at 16:39 UTC is how [EU/SWE] Playstar - SOLO - LARGE MAP wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world in play was created 13 days 5 hours ago. Its tags publish a wipe schedule of one wipe every two weeks.

Lists and filters

How should you read the tags on [EU/SWE] Playstar - SOLO - LARGE MAP?

Tags published by [EU/SWE] Playstar - SOLO - LARGE MAP, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^q (Premium): Entry needs Rust's premium status; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; EU (Europe): The server browser files it under Europe. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show [EU/SWE] Playstar - SOLO - LARGE MAP?

On Rust Metrics, [EU/SWE] Playstar - SOLO - LARGE MAP sits in these lists: EU Rust servers, checked, Rust community servers: live readings and Vanilla Rust servers, live. Check: filters. On the server list it appears under these: Region: Europe; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Game mode: Premium; Server tag: Biweekly ^b, Vanilla ^v, Premium ^q and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Players now: At least 10.

Player count

What position does [EU/SWE] Playstar - SOLO - LARGE MAP hold among Rust servers?

Player hours over the last seven days put [EU/SWE] Playstar - SOLO - LARGE MAP at #967, #417 in Europe, in the top 4% of all ranked servers.

What is the population on [EU/SWE] Playstar - SOLO - LARGE MAP?

10 of 50 slots are filled on [EU/SWE] Playstar - SOLO - LARGE MAP right now. Check: players over seven days. Average 10, peak 24. The last 48 hours peaked at 21:00 UTC, averaging 12 players at that hour.

Operator and location

What location is [EU/SWE] Playstar - SOLO - LARGE MAP hosted in?

[EU/SWE] Playstar - SOLO - LARGE MAP gives Europe as its location, with the EU tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 192.121.44.42:28016.

What Rust version is [EU/SWE] Playstar - SOLO - LARGE MAP on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by [EU/SWE] Playstar - SOLO - LARGE MAP. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for [EU/SWE] Playstar - SOLO - LARGE MAP?

Reading: 56 server fps on average across the last 48 hours. It never dropped below 47. Check: entities. The peak was 190,789, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 4,935 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is [EU/SWE] Playstar - SOLO - LARGE MAP, and is it online now?

[EU/SWE] Playstar - SOLO - LARGE MAP reports online. Status: normal. Reading: uptime. About 17 hours ago it restarted, on its own count. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does [EU/SWE] Playstar - SOLO - LARGE MAP enforce, and what are its settings?

Reading the name gives no gather rate for [EU/SWE] Playstar - SOLO - LARGE MAP. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. Plugin count: Oxide. Vanilla is the label it uses: the stock game: Facepunch's rates, kits and rules, unchanged. Entry needs Rust's premium status. Check: anti-cheat. VAC, Valve's system, is on.

What map is [EU/SWE] Playstar - SOLO - LARGE MAP on?

From seed 3587689, the game generates the procedural map on [EU/SWE] Playstar - SOLO - LARGE MAP. Its size is 5,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How do you connect to [EU/SWE] Playstar - SOLO - LARGE MAP?

Press F1 in Rust and enter client.connect 192.121.44.42:28016. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. Entry needs Rust's premium status. https://discord.com/invite/gxJm7Pv is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^b,^v,EU,gmrust,cs168909,^q,ts8,^o

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Mods and access

^q
Premium Entry needs Rust's premium status.
^o
Oxide Check: framework. Oxide (uMod) handles plugins.

Region

EU
Europe The server browser files it under Europe.

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.