TEST SERVER | 3X | [TR]
Key statistics
the figures behind the quote- Players now
- 1/ 150 1% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- – score 0
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 33d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- 3x read from the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 13 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestWipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | Atlas - EU 3x | No BPs | MondaysEU · groups of 16+ · 3x · weekly · 315 on average | 311/350 | ▲+4+1.3% | |
| 2 | Vital Rust - EU Mondays | 3x | No BPsEU · groups of 14+ · 3x · weekly · 143 on average | 107/150 | ▼−17−13.7% | |
| 3 | HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 125 on average | 43/100 | ▼−48−53.0% | |
| 4 | HollowServers.co 3x Solo/Duo/Trio |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 120 on average | 222/215 | ▼−232−51.1% | |
| 5 | AceRust.com 3x Solo/Duo|LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 106 on average | 75/100 | ▼−134−64.2% | |
| 6 | [US] Upsurge Main | 3x Vanilla | 10/13NA · groups of 12+ · 3x · weekly · 95 on average | 396/450 | ▲+373+1609.4% |
Quick answers
from the figures on this pageMap and Rules
How is TEST SERVER | 3X | [TR] configured in terms of rules and settings?
A gather rate of 3x appears in the name of TEST SERVER | 3X | [TR]. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. The server browser lists it as Modded: plugins or settings change the game. Plugin count: Oxide. VAC is active.
What is the current map on TEST SERVER | 3X | [TR]?
A procedural map runs on TEST SERVER | 3X | [TR], created by the game.
Player Count
How many players does TEST SERVER | 3X | [TR] have?
At present, TEST SERVER | 3X | [TR] is offline; the last sighting was 30 days 16 hours ago.
Wipe Schedule
On what cycle does TEST SERVER | 3X | [TR] wipe?
The record holds too few of TEST SERVER | 3X | [TR]'s wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. 33 days 11 hours ago the current world was created.
Server Info
Where can TEST SERVER | 3X | [TR] be found?
No region is published by TEST SERVER | 3X | [TR]. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. You can reach it at 212.133.232.105:28015.
TEST SERVER | 3X | [TR] runs which version of Rust?
Rust network protocol 2633 and build 163493 on Windows is what TEST SERVER | 3X | [TR] runs. Joining requires the same protocol on your game, which Steam updates.
How reliable is TEST SERVER | 3X | [TR] and is it currently online?
No response from TEST SERVER | 3X | [TR]. It was last seen 30 days 16 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. 13 September 2026 is when Rust Analytics first saw it.
Tags and Rankings
How should you interpret the tags on TEST SERVER | 3X | [TR]?
These tags are published by TEST SERVER | 3X | [TR] and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp150 (Max players): Capacity: 150 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2633 (Protocol): Protocol 2633: matching game versions are required to join; cs163493 (Build): It runs build 163493; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also carry its current players, queue and world creation time; this page shows them at the top.
On Rust Analytics, which lists and filters feature TEST SERVER | 3X | [TR]?
These Rust Analytics lists include TEST SERVER | 3X | [TR]: 3x Rust servers and Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
Connection
What is the process to join TEST SERVER | 3X | [TR]?
Type client.connect 212.133.232.105:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp150,ptrak,$r?,v2633,gmrust,cs163493,ts8,^o^z
Game
gmrust
mp150
ts8
v2633
cs163493
ptrak
$r?
Mods and access
^o
^z
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.