Telegram RegisterThe public register of Telegram
Telegram profile photo for Royal Challengers Bangalore fans

Channel

Royal Challengers Bangalore fans

@RCB_FANS_STATUS

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,877subscribers

-48 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001912069607
TypeChannel
Username@RCB_FANS_STATUS
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live29 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/RCB_FANS_STATUS

Growth

2,8772,9252,9016 August 2026 — 2,925 subscribers6 August 2026 — 2,925 subscribers9 August 2026 — 2,916 subscribers12 August 2026 — 2,913 subscribers16 August 2026 — 2,904 subscribers19 August 2026 — 2,895 subscribers22 August 2026 — 2,893 subscribers26 August 2026 — 2,881 subscribers29 August 2026 — 2,877 subscribers6 August 202629 August 2026
9 measurements spanning 23 days, net -48. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,870–2,932 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 00:242,877-4
26 Aug 2026, 03:082,881-12
22 Aug 2026, 17:032,893-2
19 Aug 2026, 09:182,895-9
16 Aug 2026, 05:542,904-9
12 Aug 2026, 10:242,913-3
9 Aug 2026, 10:322,916-9
6 Aug 2026, 06:162,925no change
6 Aug 2026, 06:082,925first reading

Engagement

20 posts held, back to 29 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 31 May 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

183 reactions across 20 posts, in 4 distinct kinds. The most used accounts for 61.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥11261.2%
6435.0%
👏42.19%
👍31.64%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 183reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 29 March 2026 to 31 May 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

31 May 2026, 18:15 UTC≈1,460 views12 reactionsread 7 August 2026
Photo

𝘾.𝙃.𝘼.𝙈.𝙋.𝙄.𝙊.𝙉.𝙎 🏆🏆

🔥93

29 May 2026, 20:13 UTC≈1,610 views8 reactionsread 7 August 2026
Photo

𝐓𝐇𝐄. 𝐅𝐈𝐍𝐀𝐋. 𝐂𝐇𝐀𝐏𝐓𝐄𝐑. ❤️‍🔥🏆 7️⃣3️⃣ matches. ⚔️ 6️⃣3️⃣ days. 📅 1️⃣0️⃣ teams. 🙌 And, it all comes down to Sunday: the #TATAIPL 2️⃣0️⃣2️⃣6️⃣ finale - RCB vs GT. ❤️🔥

🔥5👏21

28 May 2026, 12:41 UTC≈1,300 views12 reactionsread 7 August 2026
Photo

He’s 𝑺𝒎𝒐𝒐𝒕𝒉, He’s 𝑫𝒂𝒏𝒈𝒆𝒓𝒐𝒖𝒔, He’s 𝑷.𝒀.𝑻. (𝑷𝒓𝒆𝒕𝒕𝒚 𝒀𝒐𝒖𝒏𝒈 𝑻𝒉𝒊𝒏𝒈), He’s the 𝑻𝒉𝒓𝒊𝒍𝒍𝒆𝒓. He will 𝑩𝒆 𝑻𝒉𝒆𝒓𝒆, to 𝑯𝒆𝒂𝒍 𝒕𝒉𝒆 𝑾𝒐𝒓𝒍𝒅, to 𝑪𝒂𝒓𝒆 𝑨𝒃𝒐𝒖𝒕 𝑼𝒔… He's not 𝑩𝒊𝒍𝒍𝒊𝒆 𝑱𝒆𝒂𝒏. He’s 𝑩𝒉𝒖𝒗𝒏𝒆𝒔𝒉𝒘𝒂𝒓 𝑲𝒖𝒎𝒂𝒓. 🙌❤️‍🔥 RCB ADMIN POSTED BHUVI ANTHEM ❤️❤️

🔥84

17 May 2026, 14:15 UTC≈1,440 views7 reactionsread 7 August 2026
Photo

RCB WON BY 23 RUNS ❤️❤️ AND QUALIFFIED FOR PLAYOFFS IPL2026

🔥6👏1

17 May 2026, 14:15 UTC≈1,630 views9 reactionsread 7 August 2026
Photo

PLAYER OF THE MATCH 🥇 VENKATESH IYER 😎😎 73*(40) 8 FOURS AND 4 SIXES 🔥🔥 THALAPATHY VIJAY CELEBRATION 🎉🎉

🔥72

13 May 2026, 18:52 UTC≈1,580 views6 reactionsread 7 August 2026
Photo

MOST HUNDREDS IN IPL HISTORY 🚨 Virat Kohli - 9* Jos Buttler - 7 Chris Gayle - 6 KL Rahul - 6

🔥6

10 May 2026, 19:34 UTC≈1,330 views8 reactionsread 7 August 2026
Photo

PLAYER OF THE MATCH 🥇 4-0-23-4 AND IMPORTANT SIX 🔥🔥🔥 BHUVANESHWAR KUMAR 🐐

🔥7👍1

10 May 2026, 19:34 UTC≈1,410 views9 reactionsread 7 August 2026
Photo

FAN FAVOURITE PLAYER OF THE MATCH 🥇 73(46) 4 FOURS AND 5 SIXES 🔥 🔥 KRUNAL CLUTCH PANDYA 💀💀

🔥9

10 May 2026, 18:18 UTC≈1,160 views7 reactionsread 7 August 2026
Photo

RCB WON BY 2 WICKETS ❤️ BHUVANESHWAR KUMAR THE HERO 🫡🫡

🔥52

24 Apr 2026, 18:05 UTC≈1,560 views16 reactionsread 7 August 2026
Photo

50TH WIN AT CHINNASWAMY ❤️‍🔥

8🔥7👍1

17 Apr 2026, 09:41 UTC≈1,880 views14 reactionsread 7 August 2026
Photo

Green jersey confirmed for RCB tomorrow against DC Afternoon game at home 🏠

12🔥2

Showing the 12 most recent of 20 posts we hold for @RCB_FANS_STATUS. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 229,755 of 1,627,068entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 29 August 2026 — this entry's latest reading, not the date you are reading this.

“Royal Challengers Bangalore fans” (@RCB_FANS_STATUS), 2,877 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/RCB_FANS_STATUS.

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.