RUST METRICSFlight deck · live data
Data live Servers11,792 Players68,594 Populated3,568 Fresh wipes 3 h191 Scan5 min
‹ All servers148.222.43.181:28016
Offline Full Queue Fresh wipe Wipe due No query

Jungtown ep 2

Offline 148.222.43.181:28016 checked 21d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 10 20 30 40 PAX 0 /40

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,903top 72%
Last wipe32d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Sep30 Sep3 Oct7 Oct10 Oct14 Oct

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

PLAN

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 peak7players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 26 Sep, 19:28 UTC32d ago 7 – 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Reset cycle

What happens on Jungtown ep 2 when wipe day comes?

The busiest point of its recent wipes drew 7 players on average. After the latest wipe, numbers topped out at 2 hours.

When does Jungtown ep 2 wipe?

To tell the rhythm of Jungtown ep 2, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 32 days 17 hours ago the current world was made.

Lists and filters

Which tags does Jungtown ep 2 carry, and what do they mean?

These are the tags Jungtown ep 2 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp40 (Max players): 40 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Jungtown ep 2 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Jungtown ep 2: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does Jungtown ep 2 hold among Rust servers?

Player hours over seven days put Jungtown ep 2 at #15,903, in the top 72% of all ranked servers.

What player count does Jungtown ep 2 carry?

Jungtown ep 2 is not responding; status offline, last seen 21 days 17 hours ago.

Server

What location is Jungtown ep 2 hosted in?

No region tag on Jungtown ep 2. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 148.222.43.181:28016.

What Rust version is Jungtown ep 2 on?

Rust network protocol 2633 and build 165217 on Linux is the build Jungtown ep 2 runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Jungtown ep 2, and is it online now?

Check: connection. Jungtown ep 2 is offline at this moment. Last contact was 21 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 26 September 2026, recorded by Rust Metrics.

Map and rules

How is Jungtown ep 2 configured, and what rules are in force?

Reading the name gives no gather rate for Jungtown ep 2. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is Jungtown ep 2 on?

Procedural map on Jungtown ep 2, made by the game's generator.

Connection

How do you connect to Jungtown ep 2?

To join: start Rust, press F1 and type client.connect 148.222.43.181:28016. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp40,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp40
Max players 40 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Game build reading: 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

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.