Offline 142.179.235.197:28015 checked 23d ago
Mc Testing Stuff
Connect
srv = rust.server("142.179.235.197: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. 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 70% of all ranked servers. 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 6d 23h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 23h | 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 19:12 UTC FW27d ago | 1 | NaN | running | 0 |
# 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())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 142.179.235.197:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 19:12 UTC
- hostname
- –
- first seen
- 28 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 512 on average | 321/375 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 317 on average | 440/475 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 280 on average | 970/1000 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 276 on average | 46/100 |
| 4 | eulongtest (private perf box) | EU · groups of 14+ · monthly · 267 on average | 480/8 |
| 5 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 265 on average | 979/1000 |
Quick answers
From the figures on this page.
Player counts
How does Mc Testing Stuff compare in the rankings?
Player hours over seven days put Mc Testing Stuff at #15,785, in the top 70% of the ranked set.
How full does Mc Testing Stuff run?
The current row shows Mc Testing Stuff offline; the last response was 23 days 18 hours ago.
Server data
Which Rust version is Mc Testing Stuff on?
Rust network protocol 2634 and build 166652 on Windows is what Mc Testing Stuff runs. Joining needs the same protocol on your game; Steam handles the update.
Is Mc Testing Stuff up, and what does its uptime show?
The latest sample has Mc Testing Stuff offline, with a last sighting 23 days 18 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 28 September 2026.
Where does Mc Testing Stuff sit?
There is no region published for Mc Testing Stuff. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 142.179.235.197:28015.
Map and rules
What rules and settings are recorded for Mc Testing Stuff?
The name Mc Testing Stuff carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. VAC is not running; Valve's anti-cheat is off.
What is the map on Mc Testing Stuff?
A procedural map runs on Mc Testing Stuff, generated by the game.
Wipe data
When does Mc Testing Stuff wipe, and on what schedule?
A single wipe each month, the force wipe, is all Mc Testing Stuff does. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 27 days 23 hours ago.
On Mc Testing Stuff, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Where does Mc Testing Stuff appear among Rust Data lists and filters?
On Rust Data, Mc Testing Stuff appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on Mc Testing Stuff hold?
Read by the game's server browser, the tags Mc Testing Stuff publishes are: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): Slot count: 500; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. 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.
Join steps
How can I connect to Mc Testing Stuff?
In Rust, F1 opens the console: type client.connect 142.179.235.197:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.