On Saturday, Rollbit player GERALT666, posting on X as @air_tag61596, observed Day 136 of waiting for a withdrawal. The account and the withdrawal were frozen, the player says, after exactly two Counter-Strike 2 esports bets, and every document Rollbit asked for, source-of-funds proof included, was sent long ago. Nothing has moved since. Nothing except the number.

Two Bets, One Frozen Account

The freeze, as GERALT666 tells it, traces to a pair of wagers so ordinary the player could not figure out what the problem was. Senior support, the player says, came back asking why those matches had been bet at all. GERALT666 supplied the defense:

These were not suspicious matches. They were popular Tier-2 CS2 teams.

The follow-up objection was better still. If betting those games was somehow off limits, the player wanted to know why the lines were on the board in the first place. In GERALT666's version there is no other crime on the rap sheet: two bets, then a frozen account and a frozen withdrawal, then senior support asking the kind of question a casino usually saves for after you have won. The player put it plainly: "I genuinely thought the platform was intended for betting." So, presumably, did everyone reading the sportsbook tab.

Meanwhile, 24 Hours

Rollbit was demonstrably awake on Saturday. Early that morning, support agent michaelm was in the replies of a different player, @WhaleUnderdog, untangling the cross-chain deposit-and-instant-withdrawal mixup we covered when it first blew up. The agent's sign-off promised speed, telling that player the relevant department "typically addresses this sort of thing within 24hours."

GERALT666 found that thread and took a number.

Some sort of thing getting resolved in 24 hours, I've waiting for a response for 136 days

That is Rollbit support in one sentence, and the math is almost too neat. Twenty-four hours, times 136, is exactly 136 days. The fast lane has now lapped GERALT666's ticket once for every day of the wait. Either the compliance team has a flair for symmetry, or the only thing doing careful arithmetic in this story is the day counter.

The Ritual

By now the count has become the activity. The number is the one part of the case that still updates without fail. The player has also dated the freeze to April 14, which by the calendar lands closer to 123 days, and mentioned "120 days waiting compliance respond" elsewhere. The arithmetic has gone soft at the edges, the way it does when a wait stops being an incident and becomes a hobby. Day 136 is precise. The rest of the record is a shrug.

The player has been clear about the stakes, and they are worth keeping straight. GERALT666 wrote that the stuck balance is "a very significant amount of money" and that the freeze "has seriously affected my personal life." There is a real person on the other end of the day counter, and that person is not the joke. The joke is a support system that can promise one customer 24 hours while another file sits on a calendar for four and a half months.

The Calendar Does Not Blink

By Saturday evening GERALT666 had stopped aiming at support staff and started replying to the content calendar directly. Rollbit moderator Staron had posted the day's promotion, and it was not a compliance update.

New challenges are up on @rollbit. Good luck spinning!

GERALT666's reply, filed neatly under the giveaway, was the same status request the player has now made for 136 days: the withdrawal is pending, the account is disabled, and it has been that way since April 14. The challenges were up. The withdrawal was not. The machine kept spinning.

The day-counting reply is becoming a Rollbit genre, and GERALT666 is simply the latest entrant on the calendar. WilliamTai recently passed Day 210 running the same campaign under every Rollbit post, and the casino marked that stretch by launching a cartoon fisherman. The challenge drops and the day counts both keep coming. The difference is that only one of them is supposed to be the game.