DropSiren

Rainbet · Weekly report · 21–27 Sep 2026

Rainbet bonus codes this week (21–27 Sep 2026): 64 codes, $1,166, busiest at 01:00 UTC

64 codes on Rainbet in week 39 of 2026 (21–27 Sep 2026), $1,166 in total, busiest at 01:00 UTC, median gate $20,000.

Data: 64 codes from t.me/Rainbet_Bonus, t.me/Rainbet_Vip between 21 Sep 2026 00:00 UTC and 28 Sep 2026 00:00 UTC. Figures computed 1 Oct 2026 09:23 UTC.

64 codes landed on Rainbet between 21–27 Sep 2026 — week 39 of 2026 — adding up to $1,166. On the everyday channel that came to one code every 4h at the median. The busiest hour was 01:00 UTC. All of it is counted from Rainbet's own public posts, in UTC.

Codes tracked

64

9.1 a day across 7 days

Total face value

$1,166

$18.22 average per code

Busiest hour (UTC)

01:00

11 codes posted in that hour

Typical gap

4h

median between 36 codes on the everyday channel

What landed

The split between the channels is the part most round-ups leave out. Rainbet Bonus carried 36 codes, typically $2.50 each, on a median gate of $9,000 wagered. Rainbet VIP Bonus added 28 codes at around $25, but only to accounts over $67,500 wagered. 38% of the 64 codes with a stated value came in under $5 — small money, and that is the honest shape of this feed. Across everything, the median code paid about $0.33 per $1,000 of the gate it asked for — the number to hold in your head before you chase one. The arithmetic behind it is in our guide to how drop-code gates work on Stake.

ChannelCodesTotal valueTypical codeTypical gate (wagered)
Rainbet Bonus36$132$2.50$9,000
Rainbet VIP Bonus28$1,034$25$67,500
All channels64$1,166$18.22 avg$20,000

When they landed

00:0003:0006:0009:0012:0015:0018:0021:00
Rainbet codes per hour of the day (UTC), 21–27 Sep 2026. 64 codes in total. Peak: 01:00.
Table view
00:003
01:0011
02:001
03:000
04:000
05:005
06:000
07:000
08:000
09:005
10:000
11:000
12:000
13:0010
14:003
15:000
16:000
17:0011
18:001
19:000
20:001
21:0010
22:003
23:000

There is no schedule for these. There is a pattern, though. The single busiest hour was 01:00 UTC with 11 codes. Widen it to a three-hour window and 00:00–03:00 UTC held 15 codes, 23% of everything posted. Saturday was the heaviest day with 11 codes.

On the everyday channel the median gap between codes was 4h. The longest silence ran 12h 34m. Every one of the 7 days we watched produced at least one code. The first landed at 00:32 UTC on 21 Sep and the last at 21:48 UTC on 27 Sep.

The biggest codes

Size and gate move together, every time. The largest was $100, which needed $200,000 wagered in the 2 days before it and published 50 claims. That claim count is the whole story: once 50 people redeem it, the code is finished, whoever else was eligible. Behind it: AJUDMH3Z at $80 ($125,000 wagered), 52Z0BLLC at $80 ($125,000 wagered), KHERFSKU at $75 ($175,000 wagered). The gates this period ran from $3,000 at the low end to $200,000 at the top, with a median of $20,000.

Versus last week

Set that next to the week before it: 64 codes against 70, down 6 (9%). Total face value was unchanged at $1,166. The busiest hour moved from 13:00 to 01:00 UTC.

What it means for you

  • Know your gate before you chase. Half the codes this week wanted more than $20,000 wagered inside the window printed on the code. On the everyday channel the typical code was $2.50 against a $9,000 gate — that is the realistic one to aim at. Under the gate a code returns "not eligible" however fast you paste it, and every error message decoded covers the rest of the messages.
  • Be around 00:00–03:00 UTC. That window held 23% of this week's codes, and Saturday was the busiest day. Convert it to your own clock once and you stop missing them; the drop schedule board keeps a rolling version of this chart.
  • Claims run out faster than the window does. Rainbet prints the exact number of claims on every code (19,815 across this week), and the wager window runs 2 to 7 days depending on the code. A code with hours left on its window can already be finished — the claim count, shown on every card on the live Rainbet wire, is the number that matters.

Every code above has its own page with the exact post time, the gate, and where to paste it; the code archive keeps them after they die, and the rest of the Drop Reports covers the other platforms and the months.

How to read this: every figure above is counted from the posts Rainbet published on its own public channels, timestamped in UTC. Statuses on this site are derived from a code's age, not from any private feed — we do not know who claimed what, and no page here will pretend otherwise. Face value is what the post said, not what anyone received.

Questions people actually ask

How many Rainbet bonus codes were posted in week 39 of 2026?
64, between 21–27 Sep 2026, worth $1,166 of stated face value in total. Counted from t.me/Rainbet_Bonus, t.me/Rainbet_Vip, timestamped in UTC.
What time of day do Rainbet bonus codes drop?
In week 39 the busiest single hour was 01:00 UTC with 11 codes, and the 00:00–03:00 UTC window held 23% of them. There is no published schedule — this is measured from the posts themselves, and it moves week to week.
How much do you need to have wagered to claim these codes?
The median code in week 39 asked for $20,000 wagered inside the window printed on that code (2 to 7 days). Gates ran from $3,000 to $200,000. Below the gate the code returns "not eligible" — it is not a no-deposit bonus.
Do these codes still work?
Almost certainly not. Drop codes are shared, first come first served, and usually finish within hours of posting. This report is a record of what was published during 21–27 Sep 2026, not a list of live codes — the live ones are on Rainbet's feed on this site.

Related

Reports are written from the tracker every Monday — the codes themselves are announced as they land on the wire on Telegram. Full index: every Drop Report.

The siren goes off the second a code lands

New drops hit our Telegram channel as the wire catches them — code, value and the wagering gate. Want only the codes you can claim? Tell @DropSirenBot your 7-day volume — one message, done. Run a Discord? Connect a channel.