TPC15070=
typical test
Online 104.153.151.75:28015 checked 9m ago
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, measured since 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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.
-
01MODPlayers 49/500
-
02MODPlayers 121/100
-
03MODPlayers 64/225
-
04MODPlayers 60/700
-
05MODPlayers 12/200
-
06MODPlayers 16/1000
Quick answers
From the figures on this page.
Tags
Which lists and filters on Rust Tracker show typical test?
These Rust Tracker lists carry typical test: Modded servers, tracked live. These filters surface it on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
What do the tags mean that typical test is listed under?
These tags are published by typical test for the game's server browser to read: gmrust (Game mode): Rust survival, standard mode; mp100 (Max players): Capacity: 100 slots; ts8 (Group limit): Default team size: 8; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): No region code is set; ^o (Oxide): A plugin framework runs here: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Times
When does typical test wipe?
Too few wipes on record for typical test to show its rhythm. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. 47 hours since this world was made.
Server Details
Is typical test up, and how does its uptime hold?
Tracking shows typical test online as of now. The uptime it reports puts the last restart about 26 hours ago. Uptime stood at 0% for the last 1 full day, 0 of 24 hours online. The first sighting by Rust Tracker was 26 October 2026.
Which Rust version is confirmed on typical test?
Rust network protocol 2635 and build 168909 on Linux is what typical test runs. To join, your game must be on the same protocol; Steam handles the update.
Is typical test holding performance?
Server fps held an average of 240 across the last 48 hours, never below 239. Peak entity count: 3,864, covering buildings, deployables and all else in the world. Peak memory use: 1,472 MB. Lag, as players experience it, comes from low fps and a rising entity count.
What location is typical test hosted in?
Region: none published by typical test. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. You connect at 104.153.151.75:28015.
Population
Is typical test busy?
Tracking typical test: 0 of 100 slots filled. Over seven days: average 0, peak 1 players. Peak traffic in the last 48 hours came at 05:00 UTC, averaging 0 players.
How does typical test compare in the rankings?
Seven-day player hours put typical test at #15,070, within the top 68% of all ranked servers.
Map and Rules
Which settings and rules are confirmed on typical test?
Nothing in typical test's name states a gather rate. The game's default applies: groups can have up to 8 players. It runs survival, gather, build and raid: the standard game. Fighting and raiding between players are on. Plugins or settings change the game, and the server browser lists it under Modded. The plugin count stands at Oxide. VAC is on, Valve's anti-cheat.
Which map is loaded on typical test?
The map on typical test is procedural, size 1,000, seed 6738, generated by the game. Same size, same seed, same map. RustMaps shows it, linked from this page.
Connect
What is the way to join typical test?
Open the console in Rust with F1 after starting the game, then type client.connect 104.153.151.75:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp100
ts8
v2635
cs168909
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.