Tom Clancy's Rainbow Six Siege Cost — Numbers, Not Vibes

The useful question about cost is income per hour, and almost nobody states it.

Siege rewards knowing the building more than knowing the gun, which is why map knowledge outranks aim here. Idle income sounds appealing and is almost always the worst rate available. The cap on a given activity matters more than its headline number.

Solo versus group

There is no hidden trick here that the game is keeping from you. Group multipliers change the ranking of methods completely, which is why lists disagree. Payout figures quoted without a time attached are marketing rather than information. Do the cheap check before the expensive one — that ordering alone saves most of the frustration.

Event weeks distort every comparison, and normal weeks are what you should plan around. A method that was patched still shows up in search results for years afterwards. Most of the disagreement you will find online is two people describing different builds.

Setup cost and payback time

Setup cost only matters relative to how long you intend to keep playing. Where something depends on your platform or region, that is called out rather than glossed over. If your result differs from what is described here, note what is different first rather than starting over.

• Ignore anything that requires an external site or seller.
• Check the patch date on any figures you are comparing.
• Keep a save or backup from before you start — it costs nothing and occasionally saves an evening.
• Group up where the multiplier is meaningful.

Methods that were nerfed

The short version is near the top on purpose; the reasoning is there if you want to know why. Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. If you are coming to this after a long break, the terminology has probably moved on. It helps to understand why a step exists, because then you can adapt it when your situation is slightly different.

A single check up front replaces a lot of guessing later. Screenshots age faster than text, which is why this describes rather than shows. There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing.

What it earns per hour

If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about. What follows assumes you are on a current install and have not modified it. Anything that behaves differently on console than on PC is flagged where it matters.

Everything below is framed around the current state of Rainbow Six Siege rather than a launch-week impression. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. The developers have changed their mind about this at least once, which explains the older advice.

The loop worth repeating

Treat anything stated without a version number as provisional. The community wisdom on this is roughly half right, and the half that is wrong costs the most time. Where two approaches both work, the one with fewer moving parts is the one to keep.

Where people go wrong

• Trusting a video thumbnail that promises a result the video never actually shows.
• Treating a rare edge case as the normal behaviour and planning around it.
• Assuming a guide from an older season still describes the current version.

Siege FAQ

Do I need any mods or third-party tools for this?

No. Everything described here works with the base game on any supported platform.

Was this method nerfed?

Several popular ones were. Check the date on whatever you are reading before committing an evening to it.

Does this work the same on console and PC?

The logic is identical. Menu paths and button prompts differ, and any real difference is flagged above.

How long does this take?

Minutes if it goes cleanly, an evening if you hit the edge case in the caveats list. Neither is unusual.

That is the whole of it — if something here stops matching Rainbow Six Siege, the game changed, not the method.