StatusLive Servers online11,856 Players86,772 Populated3,806 Wiped · 3 h363 Interval5 min Date29 OCT 2026

DWG RG-S6283Server sheetchecked 11m ago

[ TH ] Thai Survive PVE

Online 103.107.198.149:28045 checked 11m ago

monthly wipes vanillamoddedoxidepve
Connect
Players now 0/ 50 0% full
7-day average0peak 3
Rank#6,283top 28%
Last wipe26d agomonthly schedule
Next wipe7d 3hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeak
00.511.5216:0001:0010:0019:0004:0013:00

Hourly average and peak, UTC.

Fig. 1Players on [ TH ] Thai Survive PVE
Fig. 2

Server performance

01020304016:0001:0010:0019:0004:0013:00

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 Oct13 Oct21 Oct29 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h. The force wipe · high confidence

wipe-day peak0players, last three wipes

Coming wipes

  1. 7d 3hThu 5 Nov, 19:00 UTCFW
  2. 35d 3hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

01234+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 0, 0 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 07:26 UTC26d ago 0 – 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01 31 / 300
02
[US] RustEZ Scourge PvE | Zombies | No Raiding | No KillingNA · groups of 8+ · monthly · 49 on average
35 / 200
03
[US] RustEZ Survival PvE | No Decay | No Raiding | No KillingNA · groups of 8+ · monthly · 38 on average
21 / 200
04
Hex US PVE Monthly 1X BiWeekly 5X | RPG | Custom Weapons | JetNA · no group limit · 1x · monthly · 35 on average
69 / 100
05
[坚果PVE]原倍养老/打怪升级/合成强化/召唤副本EA · groups of 8+ · monthly · 35 on average
38 / 100
06
Zombie Land PVE Monthly | Raids | Skills | Custom MapsNA · groups of 14+ · monthly · 34 on average
9 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

Is [ TH ] Thai Survive PVE online, and what uptime has been recorded?

At this moment [ TH ] Thai Survive PVE is online. The uptime it reports puts the last restart at about 4 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.

What does the recorded performance of [ TH ] Thai Survive PVE show?

Average server fps over the last 48 hours is 30; the lowest was 30. Counted at its highest: 109,091 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,748 MB. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for [ TH ] Thai Survive PVE?

A region is not published by [ TH ] Thai Survive PVE. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 103.107.198.149:28045.

What Rust version is recorded for [ TH ] Thai Survive PVE?

Rust network protocol 2635 and build 168909 on Windows: that is what [ TH ] Thai Survive PVE runs. To join, your game must be on the same protocol; Steam handles the update.

Counts

How many players are plotted on [ TH ] Thai Survive PVE?

0 of 50 slots on [ TH ] Thai Survive PVE are taken at the latest refresh. The seven-day mean is 0 players; the peak over the same period is 3. The 48-hour peak falls at 11:00 UTC, averaging 2 players.

What rank has been recorded for [ TH ] Thai Survive PVE?

Within the top 28% of all ranked servers: [ TH ] Thai Survive PVE at #6,283 for player hours, seven days recorded.

Schedules

What happens on [ TH ] Thai Survive PVE on the day of a wipe?

At their busiest, its recent wipes drew 0 players on average. At 0 hours after the latest wipe the crowd was at its peak.

What wipe schedule has been recorded for [ TH ] Thai Survive PVE?

Once a month, with the force wipe, is when [ TH ] Thai Survive PVE wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The current world has been in use since 26 days 7 hours ago. The tags state a wipe schedule of one wipe a month.

Rules and settings

Which rules and settings are recorded for [ TH ] Thai Survive PVE?

The name of [ TH ] Thai Survive PVE records no gather rate. The group limit is 8 players, the game's default. pve, no fighting other players, is the game mode. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Oxide. Its own label is vanilla, meaning facepunch's game, unaltered: rates, kits and rules are as shipped. Anti-cheat: VAC, from Valve, is on.

Which map has [ TH ] Thai Survive PVE loaded?

Size 4,250 with seed 1916469115: that is the procedural map [ TH ] Thai Survive PVE runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Tags

On Rust Graphs, which lists and filters contain [ TH ] Thai Survive PVE?

The Rust Graphs lists that carry [ TH ] Thai Survive PVE are: Modded Rust servers and PvE Rust servers, plotted. On the server list, these filters bring it up: Type: Vanilla and Modded; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

On [ TH ] Thai Survive PVE, what is meant by each tag?

gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): The slot count is 50; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^m (Monthly): Facepunch's force wipe brings a monthly wipe; ^v (Vanilla): Facepunch's game, unaltered: rates, kits and rules are as shipped; ^p (PvE): The world is the danger; players do not fight each other; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded are the tags [ TH ] Thai Survive PVE publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Connect

How is [ TH ] Thai Survive PVE joined?

Enter client.connect 103.107.198.149:28045 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/YEVyfMxwwv.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^m,^v,^p,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode This is vanilla survival.
mp50
Max players The slot count is 50.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build 168909 is the game build.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Wipe schedule

^m
Monthly Facepunch's force wipe brings a monthly wipe.

Difficulty

^v
Vanilla Facepunch's game, unaltered: rates, kits and rules are as shipped.

Gameplay

^p
PvE The world is the danger; players do not fight each other.

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