Channel
LuckyBear 🐻_RU🇷🇺 | Лакибир💥 | Основной чат
@lb_game_b
On this record: Growth · Engagement · Cite this entry
9,066subscribers
+1,590 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003284046629 |
|---|---|
| Type | Channel |
| Username | @lb_game_b |
| Created | Between 1 October 2025 and 28 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/lb_game_b |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 18:17 | 9,066 | +1,708 |
| 27 Aug 2026, 13:53 | 7,358 | +34 |
| 26 Aug 2026, 21:12 | 7,324 | no change |
| 24 Aug 2026, 14:16 | 7,324 | -33 |
| 20 Aug 2026, 22:36 | 7,357 | -21 |
| 18 Aug 2026, 02:22 | 7,378 | -24 |
| 14 Aug 2026, 16:16 | 7,402 | -29 |
| 11 Aug 2026, 13:53 | 7,431 | -40 |
| 8 Aug 2026, 08:15 | 7,471 | -5 |
| 7 Aug 2026, 18:06 | 7,476 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 30 August 2026 — this entry's latest reading, not the date you are reading this.
“LuckyBear 🐻_RU🇷🇺 | Лакибир💥 | Основной чат” (@lb_game_b), 9,066 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/lb_game_b.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.