StatusLive Servers online11,675 Players48,366 Populated3,000 Wiped · 3 h102 Interval5 min Date30 OCT 2026

DWG RG-S11754Server sheetchecked 2d ago

TummyRust 2x | solo-duo-trio | Weekly

Offline 216.39.240.213:28215 checked 2d ago

2x weekly wipes moddedoxide
Connect
Players now 0/ 100 0% full
7-day average0peak 1
Rank#11,754top 53%
Last wipe5d agoweekly schedule
Next wipe1d 20hSat 31 Oct, 23:26 UTC
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on TummyRust 2x | solo-duo-trio | Weekly
Fig. 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

Top 53% of all ranked servers. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Saturday 31 October, 23:26 UTC, in 1d 20h. Its weekly schedule tag · low confidence

usual gap32.2 daysbetween real wipes
wipe-day peak0players, last three wipes

Coming wipes

  1. 1d 20hSat 31 Oct, 23:26 UTC
  2. 6d 16hThu 5 Nov, 19:00 UTCFW
  3. 8d 20hSat 7 Nov, 23:26 UTC
  4. 15d 20hSat 14 Nov, 23:26 UTC
  5. 22d 20hSat 21 Nov, 23:26 UTC
  6. 29d 20hSat 28 Nov, 23:26 UTC
  7. 34d 16hThu 3 Dec, 19:00 UTCFW
  8. 36d 20hSat 5 Dec, 23:26 UTC

The first 48 hours of its last wipes

Sat 24 OctTue 22 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 1, 27 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 24 Oct, 23:26 UTC5d ago 1 – running 0
Tue 22 Sep, 19:42 UTC37d ago 0 – 32.2 days 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Magic Rust #18 — Vanilla 2x | Baйп 28.10EU · groups of 150+ · 2x · weekly · 340 on average
170 / 210
02
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10EU · groups of 300+ · 2x · weekly · 321 on average
15 / 1000
03
MIRAGE RUST | MONDAY 2x | VANILLA+ | Wipe 26.10EU · groups of 300+ · 2x · weekly · 292 on average
35 / 1900
04
Magic Rust #14 — Modded 2x (No limit) | PyccкийEU · groups of 300+ · 2x · weekly · 290 on average
21 / 100
05
РОССИЯ X2 / ДЛЯ НОВИЧКОВ / THIS IS RUST!EU · groups of 12+ · 2x · weekly · 220 on average
25 / 100
06
VANILLA x2 | GGRust #4 | Для нoвичкoв 2xEU · groups of 300+ · 2x · weekly · 132 on average
3 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

How reliable is TummyRust 2x | solo-duo-trio | Weekly, and is it online now?

Last seen 2 days 9 hours ago; right now TummyRust 2x | solo-duo-trio | Weekly is offline. 114 of 168 hours up over the last 7 full days, which is 68% of the time. On 13 September 2026 is when Rust Graphs first saw it.

What location is recorded for TummyRust 2x | solo-duo-trio | Weekly?

A region is not published by TummyRust 2x | solo-duo-trio | Weekly. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 216.39.240.213:28215.

What Rust version is recorded for TummyRust 2x | solo-duo-trio | Weekly?

Rust network protocol 2635 and build 168909 on Linux: that is what TummyRust 2x | solo-duo-trio | Weekly runs. To join, your game must be on the same protocol; Steam handles the update.

Counts

What player count is recorded on TummyRust 2x | solo-duo-trio | Weekly?

No response from TummyRust 2x | solo-duo-trio | Weekly; the server was last seen 2 days 9 hours ago. Averaged across seven days, the player count is 0, with a peak of 1.

Against other Rust servers, where is TummyRust 2x | solo-duo-trio | Weekly placed?

Over the last seven days, TummyRust 2x | solo-duo-trio | Weekly records #11,754 for player hours: the top 53% of all ranked servers.

Wipe times

On TummyRust 2x | solo-duo-trio | Weekly, what does the data show for wipe day?

The recent wipes averaged a busiest count of 0 players. At 27 hours after the latest wipe the crowd was at its peak.

What wipe schedule has been recorded for TummyRust 2x | solo-duo-trio | Weekly?

Too few of TummyRust 2x | solo-duo-trio | Weekly's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. Saturday 31 October at 23:26 UTC is the date its next wipe is due. The current world has been in use since 5 days 3 hours ago. The tags state a weekly wipe schedule.

Settings

Which settings does TummyRust 2x | solo-duo-trio | Weekly run, and what rules?

2x gather is stated in the name of TummyRust 2x | solo-duo-trio | Weekly. Eight players per group: the default for the game. It runs the survival game mode, the standard game: gather, build, raid. PvP and raiding are on. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Oxide. Anti-cheat: VAC, from Valve, is on.

Which map has TummyRust 2x | solo-duo-trio | Weekly loaded?

TummyRust 2x | solo-duo-trio | Weekly runs a procedural map of size 3,000 with seed 1337, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The map is named as follows: Custom Map.

Lists and filters

Where does TummyRust 2x | solo-duo-trio | Weekly appear among the Rust Graphs lists and filters?

The Rust Graphs lists that carry TummyRust 2x | solo-duo-trio | Weekly are: Servers with a 2x gather rate and Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.

On TummyRust 2x | solo-duo-trio | Weekly, what is meant by each tag?

Tags published by TummyRust 2x | solo-duo-trio | Weekly, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp100 (Max players): The slot count is 100; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^w (Weekly): A wipe occurs every week; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

How to join

By what method do you join TummyRust 2x | solo-duo-trio | Weekly?

Enter client.connect 216.39.240.213:28215 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. You will find its website at https://discord.com/invite/7YCnum7Ud8.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^w,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Standard survival, as Rust plays.
mp100
Max players The slot count is 100.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Wipe schedule

^w
Weekly A wipe occurs every week.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is Modded.

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.

KeyTag string decoded