This server publishes no banner
Exhibit no. 15,061Acc. 2026.15061
typical test
Rust server · in the archive since 26 October 2026
Online 104.153.151.75:28015 checked 10m ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
The record of each wipe
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.
The rhythm
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
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
Top 68% of all ranked servers. Ranked on player hours over the last seven days.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Tags, lists
What do the server tags on typical test mean?
These tags from typical test, read by the game's server browser, are: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): To join, your game has to be on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The server has no region code; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. At the top of this page you also see the current players, the queue and when the world was made, all from the tags.
Which Rust Server History lists and filters include typical test?
The Rust Server History lists that feature typical test are: Modded Rust servers: the record. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
The record
Does typical test run smoothly?
240 server fps on average over the last 48 hours, never below 239. Buildings, deployables and everything else in the world came to as many as 3,864 entities. Up to 1,410 MB of memory was used. Lag, as players feel it, has two sources: low fps and a rising entity count.
Which version of Rust does typical test run?
On Linux, typical test runs Rust network protocol 2635 and build 168909. Joining requires your game to be on the same protocol; Steam keeps it updated for you.
Is typical test online, and how reliable is it?
typical test is listed as online now. About 24 hours ago is when it last restarted, judged by the uptime it reports. The first sighting by Rust Server History was on 26 October 2026.
Where is typical test located?
No region is published by typical test. Rust Server History does not look up where the machine stands; it shows where a server says it is. You can reach it at 104.153.151.75:28015.
Wipe history
What is the wipe schedule on typical test?
Its rhythm is not yet clear: too few of typical test's wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, when every Rust server wipes. 45 hours ago its current world was made.
Player record
How does typical test rank against other Rust servers?
Player hours over the last seven days put typical test at #15,061: a place in the top 68% of all ranked servers.
How busy is typical test?
Of its 100 slots, typical test currently has 0 filled. Stored history gives a seven-day average of 0 players and a peak of 1. The busiest hour of the last 48 was 05:00 UTC, averaging 0 players.
Rules, map
What are the rules and settings on typical test?
No gather rate is stated in the name of typical test. The limit of 8 players per group is the game's default. Under game mode, the entry reads survival, gather, build, raid: the standard game. Fighting and raiding between players are permitted. Plugins or settings alter the game here, and the browser lists the server under Modded. Plugins in use: Oxide. The anti-cheat VAC from Valve is active.
Which map does typical test run?
A procedural map of size 1,000 with seed 6738 is what typical test runs, generated by the game. From this page you can view the map on RustMaps: the same size and seed give the same map.
Joining the server
How do I join typical test?
Press F1 in Rust to open the console, then enter client.connect 104.153.151.75:28015 to connect. Launch Rust from this page instead and you join through Steam with the connect already made.
The label explained
Server tags
What each tag this server publishes 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.