How to farm 20 million cloth in Rust in a single wipe and become the server's top farmer

Want articles like this for your own video to promote it on YouTube and Google? Order them through the Telegram bot @sat_sit_bot. It writes articles around your video, embeds the video and publishes them on popular niche websites (no ads). Try it free: 50 articles on us.

Oct 24, 2026 · based on the channel JTeles

Key takeaways

The target was 20,000,000 cloth in a single wipe, starting from a stock of 126,000 cloth.
The plan was completed in 7 days on a live server with viewers invited in to help farm.
A large Russian clan discovered the project and attacked with PvP, raids and base defense fights.
Clan members defended the compound while the main player was offline, which kept the farm running.
The finished farm was large enough that rendering the compound visibly lagged the server.

To farm millions of cloth in Rust, stop treating hemp as a side chore and build a dedicated farm compound with enough planters, lights, water and defenders to run around the clock. The most extreme documented version of this approach is JTeles' run from 126,000 cloth to a 20,000,000 cloth target in a single wipe, completed over 7 days on a live server with viewers invited in to help — and the project only succeeded because the farm was defended as hard as it was built. If you want to support the channel while you read, the creator's sponsor link offers a free War Thunder registration with a starter bonus.

What the 20 million cloth challenge actually involved

The challenge was a single-wipe economy race: begin with 126,000 cloth already banked, then scale production until the total hits 20,000,000 before the wipe ends. That number is not reachable by looting hemp bushes on a roam, so the run depended on a purpose-built farm base with rows of planters, cloning and a supply chain for fertilizer, water and light. The creator framed the goal as becoming Rust's #1 farmer and opened the server to viewers so that the labour could be split across many hands. Seven days was the deadline, and the clock started the moment the farm went down rather than when the first hemp was picked.

Step-by-step: how to scale a cloth farm to millions

Scaling cloth is a construction and logistics problem, not a combat one, and the order of operations matters more than raw playtime.

Bank a starting stock. The run began with 126,000 cloth, which is roughly the output of a mature small farm and gives you something to measure progress against.
Pick a location with room to expand. A mega farm needs a footprint large enough for planter rows, ceiling lights, water barrels and a defensible core, so flat ground away from a busy monument beats a cramped valley.
Build planter rows in modules. Each module should be self-contained: planters, a light source, water access and a path for the farmer to run the loop without backtracking.
Solve inputs before output. Fertilizer, water and electricity are the real bottlenecks at scale; if you cannot keep the modules fed, extra planters are wasted stone and wood.
Recruit farmers. Inviting viewers turned a solo grind into a shift system, which is the only realistic way to keep production running through sleep.
Protect the compound. Walls, turrets, doors and a roster of online defenders decide whether the farm survives the week.

A viewer who once built a 1,008-planter farm on a 5x server reported that planting and harvesting by hand took about 3 hours each way before the plant-all and harvest-all quality-of-life updates, and still yielded 17.4 million cloth. That figure is the clearest evidence that planter count, not playstyle, sets the ceiling on cloth income.

Why the biggest farm on the server becomes a target

A mega farm is a visible economic threat, and on a live server it attracts raids long before it reaches its goal. In this run a large Russian clan learned what was being built and committed to stopping it, which turned the project into a mix of PvP, raids, base defense, farming under pressure and alliances of convenience. The lesson for anyone attempting a similar build is that defence is part of the farm: turrets, compound walls, offline-safe loot rooms and a group that will log in when the alarm goes off are as important as the planter rows. The finished compound grew so large that simply looking at it caused visible server lag, which is its own kind of advertisement to every raider on the map.

How a group keeps a farm running while the owner sleeps

Offline coverage is the difference between a 7-day goal and a failed wipe. The run relied on clan members holding the base while the main farmer was offline, defending the compound and keeping production moving through the night. If you are organising something similar, agree on time zones in advance, leave shared access to the farm core for trusted players only, and keep the most valuable loot in a separate room so a single breach does not end the project. A team that treats the farm as a shared job rather than one person's project is the reason these numbers are possible at all.

Typical questions from players watching big farm runs

The most common doubts around mega-farm content are about time, server type and whether the numbers are real. A 20,000,000 cloth target sounds impossible on a vanilla schedule until you account for many players farming in shifts across 7 days; a solo player on a monthly wipe should aim for a fraction of that. Server rules matter too: higher gather and stack rates on modded servers make four-digit planter counts practical, while official servers punish that scale with upkeep and lag. And yes, the lag is real — a compound large enough to stutter the server when rendered is a genuine risk to your own raid defence, because defenders can drop frames during a fight.

All links from the video

What to take away from the run

A 20,000,000 cloth wipe is a logistics project disguised as farming: planter modules, input supply, a shift roster and a defensible compound do the work, and the hemp is almost incidental. The 126,000-cloth starting stock and the 7-day deadline set a clear pace, while the hostile clan turned the build into a running siege that had to be won at the walls as well as in the planter rows. The scale of the finished compound, big enough to lag the server, is the most concrete proof of how far the project went. JTeles documents the whole attempt, including the PvP and base defence chaos, in the video breakdown above. If you want to back the channel and pick up a free-to-play start, use the War Thunder sign-up link from the video.

Questions & answers

How long does it take to farm 20 million cloth in Rust?

In this run the target was reached within a single 7-day wipe, but only because viewers were invited onto the server and farmed in shifts. A solo player on a standard wipe should expect a fraction of that total, since planting and harvesting thousands of planters by hand is measured in hours per cycle even with quality-of-life automation.

Can you build a farm this big on an official server?

It is technically possible but painful. Official servers apply upkeep costs and performance limits, and a compound large enough to lag clients when rendered becomes a liability during raids. Most four-digit planter farms are built on modded or higher-rate servers where inputs and space are easier to manage.

What is the biggest problem when running a mega farm?

Inputs and defence, not planting. Fertilizer, water and electricity have to keep every module fed, and the base has to survive raids and offline hours. In this run a large clan actively tried to destroy the farm, so defenders holding the compound while the main farmer slept were as important as the farmers themselves.

Do you need a clan to farm millions of cloth?

A group makes it realistic. Shared farming shifts keep production going around the clock, and defenders can respond when the base is attacked while the owner is offline. Solo players can still build a profitable farm, but the ceiling on total cloth per wipe is much lower without other people covering nights and raids.

Source: I Became Rust's #1 Farmer... · Markdown version