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

Short answer

Do the setup once properly, then repeat the short loop. That ordering is where the difference sits.

  • Do the daily and weekly resets first — they are the best rate available.
  • Check the patch date on any figures you are comparing.
  • Check the version you are actually running before assuming anything is broken.

Siege rewards knowing the building more than knowing the gun, which is why map knowledge outranks aim here. Event weeks distort every comparison, and normal weeks are what you should plan around. Group multipliers change the ranking of methods completely, which is why lists disagree.

The loop worth repeating

Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. Payout figures quoted without a time attached are marketing rather than information. A method that was patched still shows up in search results for years afterwards. Nothing here assumes a particular playstyle beyond wanting the thing to work.

The cap on a given activity matters more than its headline number. Idle income sounds appealing and is almost always the worst rate available. The community wisdom on this is roughly half right, and the half that is wrong costs the most time.

Methods that were nerfed

Setup cost only matters relative to how long you intend to keep playing. There is no hidden trick here that the game is keeping from you. The developers have changed their mind about this at least once, which explains the older advice.

  • Finish the setup before starting the loop.
  • Group up where the multiplier is meaningful.
  • Read the whole sequence once before doing the first step.
  • Calculate per hour, including setup and travel.

Setup cost and payback time

If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about. None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. Screenshots age faster than text, which is why this describes rather than shows. Most of the disagreement you will find online is two people describing different builds.

Treat anything stated without a version number as provisional. Do the cheap check before the expensive one — that ordering alone saves most of the frustration. Rainbow Six Siege is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look.

What it earns per hour

The short version is near the top on purpose; the reasoning is there if you want to know why. 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.

Where something depends on your platform or region, that is called out rather than glossed over. What follows assumes you are on a current install and have not modified it. If you are coming to this after a long break, the terminology has probably moved on.

Solo versus group

If your result differs from what is described here, note what is different first rather than starting over. Where two approaches both work, the one with fewer moving parts is the one to keep. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts.

Where people go wrong

  • Grinding a method that was patched months ago because a thread still ranks well.
  • Changing five things at once and then not knowing which one helped.
  • Trusting a video thumbnail that promises a result the video never actually shows.

Siege FAQ

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.

Why do other guides describe this differently?

Most were written for an earlier version and never revisited. Compare the steps against what your build actually shows.

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

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

What if none of this works for me?

Then something in your setup differs from the assumption — version, region or platform. Check those three before anything else.

Come back to the caveats list if it does not work first time — the answer is almost always in there.