Online NA 174.138.187.138:28015 checked 9m ago
NOTIME TEST RIG 1
Connect
srv = rust.server("174.138.187.138:28016")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 20% of all ranked servers, top 41% in NA, and #289 of the quad servers (top 35%). Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 20h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 20h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:29 UTC FW27d ago | 2 | NaN | running | 1 |
| 1 | Sun 27 Sep, 21:49 UTC31d ago | 2 | held half | 3.9 days | 0 |
| 2 | Sun 27 Sep, 13:28 UTC31d ago | 2 | NaN | 0.3 days | 1 |
| 3 | Sun 27 Sep, 02:42 UTC31d ago | 3 | NaN | 0.4 days | 2 |
| 4 | Sat 26 Sep, 10:09 UTC32d ago | 3 | NaN | 0.7 days | 0 |
| 5 | Fri 25 Sep, 02:05 UTC33d ago | 2 | NaN | 1.3 days | 0 |
| 6 | Thu 24 Sep, 01:31 UTC34d ago | 2 | NaN | 1 days | 1 |
# 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.
display(srv.map, srv.info())
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | WIPED ●ZOMBIE● Sinister Rust PVP|Raidable Base|SkillTree | NA · quad · monthly · 1 on average | 0/75 |
| 1 | Reddit.com/r/PlayRust - US Monthly Quad | NA · quad · monthly · 13 on average | 5/200 |
| 2 | RustForNoobs.com | Solo Duo Trio Quad | Monthly | US | NA · quad · monthly · 3 on average | 2/150 |
| 3 | Rusty Pirates | No Decay | Monthly | No BP Wipes | NA · quad · monthly · 1 on average | 1/50 |
| 4 | Atlas - US 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip | NA · quad · 2x · monthly · 242 on average | 227/250 |
| 5 | US Limitless 2x Monthly Duo/Trio/Quad|No BP Wipes|Noob Friendly | NA · quad · 2x · monthly · 143 on average | 169/200 |
Quick answers
From the figures on this page.
Population
How does NOTIME TEST RIG 1 compare in the rankings?
Ranked #4,510 on seven-day player hours, NOTIME TEST RIG 1 is #767 in North America and in the top 20% of all ranked servers. Within the quad group, its rank is #289.
How many players does NOTIME TEST RIG 1 hold at once?
Current row: 1 players on NOTIME TEST RIG 1, against 100 slots. Over the last seven days it averaged 0 players and peaked at 2. Peak hour in the last 48 hours: 21:00 UTC, mean 1 players.
Server facts
How well does NOTIME TEST RIG 1 perform?
Server fps over the last 48 hours averages 80; the floor is 62. Entity numbers reached 203,067, and that includes buildings, deployables and the rest. The memory field tops out at 6,751 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on NOTIME TEST RIG 1?
The build is Rust network protocol 2635 and build 168909 on Windows, run by NOTIME TEST RIG 1. Steam updates your game for you, but the protocol must match to join.
How reliable is NOTIME TEST RIG 1, and is it up?
Online is the state at the latest refresh for NOTIME TEST RIG 1. A restart about 15 hours ago is what its reported uptime implies. Uptime of 100% across the last 7 full days: 168 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does NOTIME TEST RIG 1 run from?
The NA tag is what NOTIME TEST RIG 1 uses to list itself in North America. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 174.138.187.138:28015.
Rules, settings, map
What rules and settings are recorded for NOTIME TEST RIG 1?
The name NOTIME TEST RIG 1 carries no gather rate. quad sets the cap: 4 players per group. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has NOTIME TEST RIG 1 loaded?
NOTIME TEST RIG 1 runs a procedural map of size 5,800 with seed 884767976, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Under map name you will find: Custom Map.
Wipe data
When does NOTIME TEST RIG 1 wipe, and how often?
Once a month NOTIME TEST RIG 1 wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 27 days 4 hours ago. A monthly wipe schedule is published in its tags.
On NOTIME TEST RIG 1, what happens on wipe day?
Recent wipes averaged 2 players at their peak. 2 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.
Lists and tags
Which lists on Rust Data hold NOTIME TEST RIG 1, and which filters?
These Rust Data lists include NOTIME TEST RIG 1: Modded Rust servers and North America Rust servers. It appears under these filters on the server list: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: Quad; Wipe schedule: Monthly.
Which meanings do the tags on NOTIME TEST RIG 1 hold?
These tags are published by NOTIME TEST RIG 1 and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp100 (Max players): The server lists 100 slots; ts4 (Group limit): No team may exceed 4; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; NA (North America): In the server browser it sits under North America. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way into NOTIME TEST RIG 1?
In Rust, F1 opens the console: type client.connect 174.138.187.138:28015. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://notime-x5-rust.tebex.io/.
