RUST METRICSFlight deck · live data
Data live Servers11,748 Players63,000 Populated3,404 Fresh wipes 3 h200 Scan5 min
‹ All servers147.93.160.205:28915
Offline Full Queue Fresh wipe Wipe due No query

In Rust we trust

Offline 147.93.160.205:28915 checked 20d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,854top 72%
Last wipe50d agono schedule published
Next wipe–no wipe 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, 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
15k10k15k20k20 Sep25 Sep30 Sep5 Oct10 Oct15 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 wipe timing does In Rust we trust follow?

The rhythm of In Rust we trust's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 50 days 13 hours ago.

Tags

Which tags does In Rust we trust carry, and what do they mean?

Tags published by In Rust we trust, read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Game build reading: 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does In Rust we trust appear in Rust Metrics lists and filters?

On Rust Metrics, In Rust we trust sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does In Rust we trust sit in the rankings?

Ranking for In Rust we trust: #15,854 on seven-day player hours, top 72% of all ranked servers.

How full does In Rust we trust get?

Status for In Rust we trust: offline. Last seen 20 days 11 hours ago.

Server details

Where does In Rust we trust sit?

Reading: location. In Rust we trust gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 147.93.160.205:28915.

What Rust version is In Rust we trust on?

Reading: In Rust we trust, Rust network protocol 2633 and build 164530, Windows. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on In Rust we trust, and is it online?

Check: connection. In Rust we trust is offline at this moment. Last contact was 20 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

How is In Rust we trust configured, and what rules are in force?

No gather rate appears in the name: In Rust we trust. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is off.

What map is In Rust we trust on?

Check: map. Procedural, size 1,500, seed 1700359132, generated by the game on In Rust we trust. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Join

What do you do to join In Rust we trust?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmvanilla,cs164530,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build Game build reading: 164530.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock game.

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.