CS2 case farming calculator.

How the math works

• Weekly gross = accounts × avg weekly drop value × sell-through rate
• Monthly gross = weekly gross × 4.33 (average weeks per month)
• Monthly net = monthly gross − monthly fixed costs − (monthly gross × ban-loss rate)
• Total upfront cost = accounts × Prime cost per account
• Cumulative net = monthly net × time horizon
• Break-even month = ceil(total upfront cost ÷ monthly net), or "never" if monthly net is zero or negative

What this calculator does not model

• Drop pool rotation. Valve refreshes the active case pool every few months, which moves the average drop value up or down. The current $1.60 midpoint is a snapshot.
• Hardware that needs replacing mid-horizon. Amortization is a flat monthly cost here.
• The time you spend operating the farm. Your time has a cost; this calculator does not put a dollar on it.
• Variance. Real drop value swings week to week, especially around CS2 patches. This calculator gives you a midpoint, not a range.
• Tax. Your jurisdiction may treat in-game item sales as taxable income. This calculator does not.

The model is intentionally simple so you can sanity-check it against your own spreadsheet. If you want a more sophisticated model, fork the page source.

Why these defaults?

Every slider on this cs2 case farming calculator ships with a default that reflects a mid-range starter farm rather than a best-case or worst-case scenario. The intent is to give a new operator a believable starting picture, then to nudge them to replace every number with their own as soon as they have one.

• 10 accounts. A mid-range starter fleet. Smaller than a serious operator runs, larger than a single-PC hobbyist. Big enough to test isolation and walkbot pacing, small enough that a first ban wave does not end the experiment.
• $1.60 weekly drop value. The publicly reported midpoint of recent active case pools on the Steam Market. The real number swings every Valve rotation; cross-check with the current Steam Market pages for whatever case is dropping this week.
• 90 percent sell-through. Accounts for drops that get held back for price appreciation, drops that sit in inventory because they are part of an active case pool no operator wants to flood, and items that move slower than the rest.
• 6 months horizon. Long enough to clear the upfront Prime spend on most input combinations. Short enough that the model does not pretend to predict a CS2 economy a year out.
• $65 monthly fixed. Roughly hardware amortization plus electricity; the default assumes $0 panel cost, set this to ~$7/month if you subscribe to MonkePanel. Adjust upward for paid panels, dedicated colocation, or a higher local power tariff.
• $14.99 Prime. Steam direct price for the Prime upgrade. Greymarket alternatives exist but carry their own risk profile; building your own clean Primes is the path we point operators toward.
• 3 percent monthly ban-loss. Conservative for a properly isolated farm, optimistic for an unisolated one. Operators with strong isolation discipline see lower numbers; setups that share a fingerprint across many accounts see much higher numbers in cluster ban waves.

How operators use this in practice

The cs2 case farming calculator is built for three operator decisions, all of which involve money on the table. Each one uses the same sliders but reads different output cards.

Sanity-checking a small farm before buying more accounts. An operator running ten to twenty accounts sets the inputs to match their current month: real drop value from their last four weekly resets, real fixed costs from their last electric bill, real ban-loss from how many accounts they have actually lost. If the monthly net is positive and stable, scaling to thirty or forty accounts is a different question than scaling from zero. If the monthly net is barely positive at the current size, adding more accounts on the same fingerprint will not fix the math; it will compound the cluster-correlation risk.

Modeling break-even before investing in dedicated hardware. Anyone considering a second PC, a small server, or a colocation slot can drop their projected hardware amortization into the monthly fixed costs slider, add the account count that hardware can isolate, and read the break-even card. If the break-even month is longer than the realistic life of the hardware, the upgrade does not pay for itself and the operator should either rethink the hardware choice or scale on the existing rig.

Deciding whether to scale up or pause. The cumulative net card and the verdict line under it are the easiest gut-check. A negative cumulative net over the chosen horizon is a clear signal to either pause and improve inputs or to walk away. A modest positive cumulative net argues for staying at the current scale and only adding accounts as fingerprint isolation improves. A strong positive net at a small account count is the rare green-light pattern that justifies cautious expansion.

Worked example: 20-account farm

A worked example helps anchor the cs2 case farming calculator outputs to a single concrete scenario. The numbers below are illustrative; replace each one with your own farm's actual figures before making any decision that involves money.

Inputs. 20 accounts. $1.60 average weekly drop value per account. 90 percent sell-through. 12-month horizon. $120 monthly fixed costs (a higher amortization figure for the second machine needed to isolate 20 accounts cleanly). $14.99 Prime per account, one-time. 5 percent monthly ban-loss rate (a deliberately conservative figure for a fresh farm still learning isolation discipline).

Formulas in plain English. Weekly gross equals accounts times drop value times sell-through. Monthly gross equals weekly gross times the average 4.33 weeks per month. Monthly ban-loss dollars equals monthly gross times the ban-loss rate. Monthly net equals monthly gross minus monthly fixed costs minus monthly ban-loss dollars. Upfront cost equals accounts times Prime cost. Cumulative net equals monthly net times the time horizon. Break-even month equals the ceiling of upfront divided by monthly net, or "never" if monthly net is zero or negative.

Resulting numbers. Weekly gross: 20 times $1.60 times 0.90 equals $28.80. Monthly gross: $28.80 times 4.33 equals roughly $124.70. Monthly ban-loss dollars: $124.70 times 0.05 equals roughly $6.24. Monthly net: $124.70 minus $120 minus $6.24 equals roughly negative $1.54. Cumulative net over 12 months: roughly negative $18.50. Upfront Prime cost: 20 times $14.99 equals $299.80. Break-even at these inputs: never, because the monthly net is negative.

The takeaway is not "20 accounts do not work". The takeaway is that at $1.60 drop value, 5 percent ban-loss, and $120 monthly fixed, the math does not pencil out and at least one input has to move. Push drop value up by choosing a stronger weekly window, push fixed costs down by consolidating on a single host, push ban-loss down through cleaner isolation. Then rerun. That iterative loop is the entire reason the calculator exists. For the framework around reading the answer (which scenario you are actually in, and what to do before you decide), see is CS2 case farming worth it in 2026.