
Channel
CricBrain
@CricbrainAB
On this record: Growth · Engagement · Telegram's recommendations · Cite this entry
4,478subscribers
-86 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001573284561 |
|---|---|
| Type | Channel |
| Username | @CricbrainAB |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/CricbrainAB |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 23:36 | 4,478 | -10 |
| 3 Sept 2026, 19:59 | 4,488 | -12 |
| 3 Sept 2026, 12:49 | 4,500 | no change |
| 31 Aug 2026, 05:25 | 4,500 | -8 |
| 28 Aug 2026, 04:34 | 4,508 | -15 |
| 24 Aug 2026, 18:57 | 4,523 | -10 |
| 20 Aug 2026, 22:43 | 4,533 | -13 |
| 17 Aug 2026, 22:55 | 4,546 | -16 |
| 14 Aug 2026, 16:36 | 4,562 | -2 |
| 13 Aug 2026, 12:45 | 4,564 | 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@fantasygram7 · 53,104
Telegram ranks this channel #1 of 66 here — alongside 65 others — read 24 August 2026
@morbestfantasy1 · 67,861
Telegram ranks this channel #9 of 50 here — alongside 49 others — read 20 August 2026
@kulwinderzzz · 32,505
Telegram ranks this channel #15 of 38 here — alongside 37 others — read 5 September 2026
@FantasyCricketAnna · 44,651
Telegram ranks this channel #17 of 51 here — alongside 50 others — read 27 August 2026
@DevanshuGuptaTG · 66,512
Telegram ranks this channel #18 of 60 here — alongside 59 others — read 20 August 2026
@Dream11Teamsfree8 · 48,641
Telegram ranks this channel #28 of 63 here — alongside 62 others — read 25 August 2026
@grandleagueexpertranu · 63,496
Telegram ranks this channel #28 of 56 here — alongside 55 others — read 21 August 2026
@d11teams · 55,562
Telegram ranks this channel #33 of 52 here — alongside 51 others — read 23 August 2026
@FantasyLossCover · 128,443
Telegram ranks this channel #38 of 60 here — alongside 59 others — read 13 August 2026
@FBuzz11 · 88,334
Telegram ranks this channel #42 of 58 here — alongside 57 others — read 17 August 2026
@sfgfamily · 78,404
Telegram ranks this channel #61 of 65 here — alongside 64 others — read 18 August 2026
@TheFantasycricketgeek · 46,059
Telegram ranks this channel #72 of 74 here — alongside 73 others — read 27 August 2026
This channel appears in 12 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“CricBrain” (@CricbrainAB), 4,478 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/CricbrainAB.
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.