Statistical profileOnline
Testing
90.146.82.82:28035 checked 6m ago
Connect to this server
1. Main points
Players now
0/ 10
0% full
7-day average
0
peak 1
Rank
#15,080
top 68%
Last wipe
4d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- There were 0 players on it, 0% of its 10 slots.
- Over the last seven days it averaged 0 players, with a peak of 1.
- It ranks #15,080 of all ranked servers, the top 68%, on player hours over the last seven days.
- Its current map went up 4d ago.
2. Players
Figure 1: Players on Testing
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 68% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipe-day peak
1
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 4 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 22:03 UTC4d ago | 1 | – | running | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of Testing
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of Testing
What the server publishes and what was recorded
| Address | 90.146.82.82:28035 |
|---|---|
| Region | – |
| Max players | 10 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 23 Oct 2026, 22:03 UTC |
| Hostname | – |
| First seen | 6 Oct 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 157 on average | 93 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 127 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 97 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 40 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 7 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 17 / 1000 |
10. Quick answers
From the figures on this page.
Wipe schedule
When does Testing wipe, and how often?
The rhythm of Testing's wipes cannot yet be told: too few are on record. A force wipe takes place monthly for every Rust server, with the next on Thursday 5 November at 19:00 UTC. 4 days 8 hours have passed since this world was made.
How is wipe day run on Testing?
The average busiest point of its recent wipes drew 1 players. 4 hours after the latest wipe, the crowd peaked.
About the server
What does the record show for the uptime and current status of Testing?
Testing is online at the time of this release. A total of 168 of 168 hours were up over 7 full days, which is 100% of the time. The first sighting of it by Rust Census was on 6 October 2026.
Which location does Testing run from?
A region is not published by Testing. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. 90.146.82.82:28035 is its address.
Which Rust version is Testing running?
This release lists Testing on Rust network protocol 2635 and build 168909, running on Linux. To join, your game has to be on the same protocol; Steam handles the update.
Population
What population has been recorded on Testing?
At counting time Testing recorded 0 players across 10 slots. This release records a seven-day average of 0 players and a peak of 1.
In the rankings of Rust servers, where is Testing placed?
For seven-day player hours, Testing is ranked #15,080, placing it in the top 68% of all ranked servers.
Tags, lists
Where does Testing appear among the Rust Census lists and filters?
These Rust Census lists include Testing: Modded Rust servers, counted. Under these filters it comes up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on Testing carry?
These are the tags Testing publishes for the game's server browser to read: gmvanilla (Game mode): This is vanilla survival; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team, which is the game's default limit; v2635 (Protocol): Protocol 2635 is required; a different version cannot join; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game on this modded server; ^y (Carbon): Plugins are handled by Carbon on this server. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Settings and map
Which map has been recorded for Testing?
A procedural map runs on Testing, generated by the game.
On Testing, what rules and settings are in force?
No gather rate is given in the name of Testing. 8 players is the group limit, the game's default. It runs survival, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings alter the game. The plugin count is Carbon. The server runs VAC, Valve's anti-cheat.
Connecting
What steps are needed to join Testing?
Enter client.connect 90.146.82.82:28035 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp10,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y
Game
gmvanilla | Game mode This is vanilla survival. |
|---|---|
mp10 | Max players 10 slots are available. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2635 | Protocol Protocol 2635 is required; a different version cannot join. |
cs168909 | Build Game build: 168909. |
ptrak | Networking The network layer is RakNet, the game's standard. |
$r? | Region code No region code is set. |
Mods and access
^z | Modded Plugins or settings alter the game on this modded server. |
|---|---|
^y | Carbon Plugins are handled by Carbon on this server. |
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.