Most players reconstruct a session from memory, and memory is a poor accountant. It remembers the big win, forgets the twenty low-stake spins that preceded it, and routinely misattributes a shrinking balance to “bad luck” rather than to the actual mechanics of stake times volume. Casushi Casino keeps a record of every spin and transaction, and reading it properly turns guesswork into a bankroll audit. This guide shows how to pull that history apart into two numbers, spin count and total staked, and use them to answer the only question that matters after a losing session: did the volume drain you, or the stake size?
Where Casushi stores your spin and transaction history
Casushi Casino exposes two separate record sets, and conflating them is the first mistake. Game history logs individual rounds: the game played, the stake per spin, the result, and the timestamp. Transaction history logs money movement: deposits, withdrawals, bonus credits, and the net effect of play on your balance. You need both to reconcile a session, because game history tells you what you did and transaction history tells you what it cost.
Access sits inside your account dashboard once you are logged in. The game history view can be filtered by date range and by game, which matters more than it sounds: a session on Big Bass Splash and a session across twenty different slots produce very different audit pictures, and mixing them hides the pattern. Set the range to the session you want to examine, not to the calendar month, or the numbers will not line up with your budget.
Keep the promo code you used to hand. If you registered with WELCOME2026 to claim the 40 free spins welcome offer, free spin rounds may appear in game history with a zero or nominal stake, because the spin was funded by the bonus rather than your balance. Those entries belong in the volume count but not in the staked total, and separating them is what keeps the audit honest.
Reconciling spin count against total staked
The audit rests on a simple identity: total staked equals average stake multiplied by number of spins. If you know any two of those figures, you can derive the third, and the derived figure is usually the one your memory has wrong. Pull the total staked from transaction history for the session window, count the spins from game history, and divide. The result is your true average stake, not the stake you think you played.
Run the reconciliation in this order to avoid double counting:
- Fix the session window by timestamp, using the first deposit or first spin of the session and the point you stopped.
- Note the opening balance from the transaction log immediately before that first spin.
- Sum all deposits made inside the window, and subtract any withdrawals.
- Count qualifying spins from game history, excluding rounds funded entirely by free spins or bonus credits.
- Read the closing balance from the transaction log after the final spin.
- Check the arithmetic: opening plus deposits minus withdrawals minus total staked, plus returns, should equal the closing balance.
If the identity does not balance, the gap is almost always a bonus credit, a free spin return, or a round that settled after you closed the app. Casushi app sessions and desktop sessions write to the same ledger, so switching devices mid-session does not create a discrepancy, but a pending round that resolves later will. Widen the window by an hour and recheck before assuming an error.
Separating volume losses from stake-size losses
This is the part memory reliably gets wrong. Two players can lose £50 in an evening and have completely different problems. The first played 500 spins at 10p; the second played 50 spins at £1. Same loss, opposite diagnosis. The first has a stake-size problem in disguise, because 500 spins at that stake is a long grind against the house edge and the loss is close to expected. The second has a variance problem: 50 spins is a tiny sample, and the loss is noise as much as anything else.
Use the recorded numbers to place yourself on that spectrum. Divide total staked by spin count to get average stake, then compare average stake to your session budget. https://casushi-online.uk/ offers additional context worth reviewing. A useful rule of thumb is that a session budget should cover at least 100 spins at your chosen stake, so a £20 budget implies a stake of 20p or less. If your history shows average stake above one hundredth of your budget, the stake size is the lever to pull, not your luck.
Then look at spin count relative to time played. A high spin count in a short window on a high-volatility slot like Big Bass Splash means you were cycling money fast, and the loss reflects exposure rather than a cold streak. A low spin count with a large stake means each individual result carried outsized weight, and a single dry run could account for the whole drawdown. The two diagnoses call for different fixes: reduce stake, or reduce session length.
Reading a worked example from the ledger
Suppose transaction history shows £60 staked across a two-hour session, and game history shows 300 spins. Average stake is 20p, which against a £60 budget sits at the boundary of sensible. The loss was £18. That is a 30% drawdown on staked turnover, well within normal variance for a slot with a house edge in the low single figures, and the number of spins means the result is statistically unremarkable. Nothing went wrong. The player simply played a reasonable stake for a reasonable number of rounds and landed on the wrong side of variance.
Now suppose the same £60 staked came from 60 spins at £1 each. The drawdown is identical, but the sample is five times smaller and the stake is five times larger relative to budget. Here the audit points at stake size: dropping to 20p would have produced 300 spins and a much smoother ride, and the same £18 loss would have represented a far longer session. Same money, different lesson. That distinction is invisible from memory and obvious from the ledger.
Turning the audit into a repeatable budget check
Once you have run the reconciliation a couple of times, it becomes a five-minute habit you can do after any session that felt heavier than expected. The point is not to relitigate every spin but to catch drift early. Stake creep is gradual: 20p becomes 25p, then 40p, and the balance falls faster without any single decision feeling reckless. The ledger catches it before your balance does.
Set a session budget in pounds before you play, convert it to a maximum stake using the 100-spin rule, and write both down. After the session, compare recorded average stake to your stated maximum. If the recorded figure is higher, you have found the leak. If it matches and you still lost, the loss is variance and the correct response is to keep the stake and shorten the session, not to chase.
Fold the wider account into the same check. Casushi is licensed by the UKGC, with Solaya Group Limited holding the licence, which means deposits and withdrawals sit behind standard verification and the transaction log is a regulated record rather than a courtesy. That has practical value for an audit: the figures you see are the figures that count. Withdrawal times and payment methods affect how quickly money leaves, not what the history shows, and the Casushi guide covers those mechanics separately if you need them.
Two further details are worth building into the routine. First, the 40 free spins welcome offer requires a £10 deposit and £10 staked on slots, and free spin winnings are paid as cash with no wagering. That combination is unusually clean for an audit, because there is no playthrough to untangle from your staked total. Second, if you take part in Drops & Wins 2026 or play the daily promotional game Daily Catch, prize credits and promotional returns will appear in transaction history as separate line items. Tag them mentally as non-stake income so they do not distort your staked figure.
Finally, keep the audit in service of responsible play rather than performance. The lobby at Casushi spans slots, live casino, roulette, blackjack and game shows, and each vertical has a different relationship between spin count and stake, so a single budget rule will not fit all of them. Use the history to see which verticals you actually play and where the money goes, set deposit limits that match, and treat the recorded numbers as the arbiter whenever memory and balance disagree. The ledger does not flinch, and that is exactly why it is worth reading.