Telegram RegisterThe public register of Telegram
Telegram profile photo for VIRAT BHAI

Channel

VIRAT BHAI

@VIRATBHAI1

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

174subscribers

-8 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002131352024
TypeChannel
Username@VIRATBHAI1
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/VIRATBHAI1

Growth

1741821788 August 2026 — 182 subscribers8 August 2026 — 182 subscribers15 August 2026 — 181 subscribers22 August 2026 — 178 subscribers29 August 2026 — 177 subscribers7 September 2026 — 174 subscribers8 August 20267 September 2026
6 measurements spanning 30 days, net -8. 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 173–183 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 15:40174-3
29 Aug 2026, 13:33177-1
22 Aug 2026, 13:45178-3
15 Aug 2026, 06:27181-1
8 Aug 2026, 12:46182no change
8 Aug 2026, 05:01182first reading

Engagement

20 posts held, back to 14 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 18 December 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

18 Dec 2025, 15:49 UTC241 viewsread 8 August 2026
Photo

यह वाला मैच जैकपॉट है भाई लोग 😍 टीम WhatsApp ग्रुप में आएगा ज्वाइन फास्ट ❤️👇👇👇👇 join👆👆 Join WhatsApp Group ✅ Join WhatsApp Group ✅ Join WhatsApp Group ✅ Join WhatsApp Group ✅

17 Dec 2025, 07:57 UTC238 viewsread 8 August 2026

BIG BESH LEAGUE 2025_26 Match 👉 4th T20 Adelaide V/s Sixers #SIXERS 🔥 Will Be Win This Mat Take First Enter 90P....... Then Second Enter 50P...... Therd Enter 25P Pr Krna Hai...... Ground Fix Report Hai Play Same Limit Daily... 20P Loss Cut Book Set Compulsory.. Channel Pin To Top And Unmute Rakhna @VIRATBHAI1

17 Dec 2025, 07:56 UTC199 viewsread 8 August 2026

🇷🇪 ABU DHABI 🇷🇪 WIN ✔️ MAHA JACKPOT MATCH ❤️😍😍🔥

16 Dec 2025, 14:22 UTC185 viewsread 8 August 2026

INTERNATIONAL T20 LEAGUE 2025 Match 👉 17th T20 Desert V/s Abu Dhabi ABU DHABI 🔥 Will Be Win This Mat Take First Enter 90P....... Then Second Enter 50P...... Therd Enter 25P Pr Krna Hai...... Ground Fix Report Hai Play Same Limit Daily... 20P Loss Cut Book Set Compulsory.. Channel Pin To Top And Unmute Rakhna @VIRATBHAI1

16 Dec 2025, 14:22 UTC160 viewsread 8 August 2026

🇱🇻 HOBART HURRICANES 🇱🇻 WIN* ✅ NON CUTTING WINNER BACK TO BACK JEET MUBARAK HO 💥💥💥💥💥💥💥💥💥💥💥💥

16 Dec 2025, 07:38 UTC134 viewsread 8 August 2026

BIG BESH LEAGUE 2025_26 Match 👉 3rd T20 Thunder V/s Hobart #HOBART 🔥 Will Be Win This Mat Take First Enter 90P....... Then Second Enter 50P...... Therd Enter 25P Pr Krna Hai...... Ground Fix Report Hai Play Same Limit Daily... 20P Loss Cut Book Set Compulsory.. Channel Pin To Top And Unmute Rakhna @VIRATBHAI1

15 Dec 2025, 14:29 UTC118 viewsread 8 August 2026

🇷🇪 RENEGADES 🇷🇪 WIN ✔️ BACK TO BACK JEET MUBARAK HO BOOM 💥💥💥💥💥💥💥💥💥💥

15 Dec 2025, 10:00 UTC120 viewsread 8 August 2026

19-21 🇷🇪 RENEGADES 🇷🇪 CLOSE RATE ✔️ LOGG CUT BOOK SET WORK DONE ✅✅✅✅

Showing the 12 most recent of 20 posts we hold for @VIRATBHAI1. 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 7 September 2026 — this entry's latest reading, not the date you are reading this.

“VIRAT BHAI” (@VIRATBHAI1), 174 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/VIRATBHAI1.

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.