On the class lists: F (37), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 1
Rank#12,370top 55%
Last wipe1h agomonthly schedule
Next wipe7d 3hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
45/ 100
D
Working its way up from the back of the class: #12,370 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
9/ 100
F
Needs to work on its frame rate: 5 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 1,104 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 55% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
··W···W
···W
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h.
The force wipe · high confidence
usual gap4.1 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
Coming wipes
7d 3hThu 5 Nov, 19:00 UTCFW
35d 3hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Sun 25 OctWed 21 OctMon 5 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 29 Oct, 13:08 UTC1h ago
–
–
running
0
Sun 25 Oct, 10:08 UTC4d ago
1
–
–
0
Wed 21 Oct, 12:50 UTC8d ago
1
halved by day 1
3.9 days
0
Mon 5 Oct, 08:05 UTC24d ago
1
halved by day 1
16.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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Twig Experiments™ leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 66.51.98.51:28030.
Is Twig Experiments™ up, and how steady is its uptime?
The server is up: Twig Experiments™ is online now. About 4 days 1 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 166 of 168 hours, or 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does Twig Experiments™ run?
It averaged 5 server fps over the last 48 hours, with a low of 5. Up to 43,434 entities were in the world, covering buildings, deployables and the rest. Up to 1,982 MB of memory was used. Players feel lag when fps drops and entities pile up.
Which Rust version is Twig Experiments™ running?
Rust network protocol 2635 and build 168909 on Linux is what Twig Experiments™ runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Twig Experiments™ wipe, and how often?
Once a month, Twig Experiments™ wipes with the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 1 hours have passed since this world was made. The tags show a monthly wipe schedule.
What should you expect from wipe day on Twig Experiments™?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 0 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. In the other wipes it slipped under half by day 1.
Population
What position does Twig Experiments™ hold in the rankings?
In the top 55% of all ranked servers, Twig Experiments™ sits at #12,370 for player hours over the last seven days.
What does the population on Twig Experiments™ look like?
Right now, 0 players are on Twig Experiments™, which has 50 slots. Averaging 0 players over seven days, it peaked at 1. Over the last 48 hours, the peak hour was 13:00 UTC, averaging 1 players.
Tags and filters
What do Twig Experiments™'s tags stand for?
You'll see Twig Experiments™ tagged with gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts0 (Group limit): You cannot form teams here; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature Twig Experiments™?
Rust Server Score lists that include Twig Experiments™: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Wipe schedule: Monthly; Last wipe: In the last 24 hours.
Server rules
Which rules does Twig Experiments™ enforce, and what are its settings?
The name of Twig Experiments™ gives no gather rate. You will find no published group limit. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Twig Experiments™ runs which map?
A procedural map of size 1,000 and seed 1337, generated by the game, is what Twig Experiments™ runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
How to join
What is the way to join Twig Experiments™?
To connect, start Rust, press F1, and type client.connect 66.51.98.51:28030. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^m,gmrust,cs168909,ts0,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts0
Group limitYou cannot form teams here.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under 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.
A term to build on. Strongest in uptime (A); population is the one to work on (F).