Rust Server TrendsSeismic network · station log
Recording Stations11,611 Players34,878 Active2,847 Wipes · 3 h62 48 h

Station XX-16838 · no signal

[DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep

Offline 141.95.34.154:28080 checked 27d ago

2x moddedcarbon
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,838
top 70%
Last wipe
33d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-16838 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep23 Sep27 Sep30 Sep4 Oct7 Oct

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

Expected events

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 peak
2players, last three wipes

The first 48 hours of its last wipes

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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 24 Sep, 17:12 UTC33d ago M0.3rising 2 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 725 on average
285/ 350
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 543 on average
170/ 150
Atlas - US 2X Monthly | Vanilla+ | No BP Wipes NA · groups of 16+ · 2x · monthly · 350 on average
148/ 200
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr EU · groups of 50+ · 2x · monthly · 324 on average
55/ 150
Magic Rust #18 — Vanilla 2x | Pyccкий EU · groups of 150+ · 2x · weekly · 323 on average
11/ 100
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 EU · groups of 300+ · 2x · weekly · 298 on average
82/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep?

[DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep runs a procedural map of size 3,500 with seed 1829923550, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep?

Going by its name, [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep runs 2x gather. At the game's default, groups can have up to 8 players. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Carbon is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep?

A reading taken now finds [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep offline; the most recent activity was 27 days 19 hours ago.

How does [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep rank against other Rust servers?

The last seven days of player hours place [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep at #16,838, in the top 70% of all ranked servers.

Operator and location

How reliably does [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep stay online?

[DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep is down at the moment; the last recorded contact was 27 days 19 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 13 September 2026 is when Rust Server Trends first recorded it.

Which region does [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep run from?

Nothing about a region comes from [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 141.95.34.154:28080.

Which Rust version is [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep running?

Rust network protocol 2633 and build 162929 on Windows is what [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep?

On average, the busiest point of its recent wipes drew 2 players. 23 hours after the latest wipe, the crowd peaked.

On what timetable does [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep run its wipes?

The rhythm of [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 33 days 11 hours is how long the current world has been running.

Tags

What do the server tags on [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep mean?

The game's server browser reads the tags [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep publishes: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs162929 (Build): The game build is 162929; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep appear?

The Rust Server Trends lists that take in [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep are: 2x Rust servers, listed live and Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 2x.

Connecting

How do you connect to [DE] JunkLab 2x | Solo | Vanilla+ | Biweekly | 50% Upkeep?

Enter client.connect 141.95.34.154:28080 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs162929,ts8,^z,^y

Game

gmrust
Game mode The game mode is standard Rust survival.
mp50
Max players 50 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs162929
Build The game build is 162929.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.