π²π° HYDERABAD π²π°DONE AND DUSTED β€π₯ ALWAYS QUEEN MASTERMIND BOSS ππ¦π΄π₯

Channel
ANJALI TIPS ... β€ππ CRICKET BETTING
@Anjali_tips_cricket_betting
On this record: Topic Β· Growth Β· Engagement Β· Posts Β· Telegram's recommendations Β· Cite this entry
4,419subscribers
-90 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 | -1001170938687 |
|---|---|
| Type | Channel |
| Username | @Anjali_tips_cricket_betting |
| Created | 15 January 2018 β measured β cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/Anjali_tips_cricket_betting |
Topic
Gambling & betting β a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channelβs own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a modelβs judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured β it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 04:22 | 4,419 | -26 |
| 15 Sept 2026, 11:55 | 4,445 | -7 |
| 11 Sept 2026, 19:21 | 4,452 | -6 |
| 6 Sept 2026, 22:58 | 4,458 | -8 |
| 2 Sept 2026, 19:24 | 4,466 | -7 |
| 30 Aug 2026, 11:55 | 4,473 | -7 |
| 27 Aug 2026, 20:25 | 4,480 | -4 |
| 24 Aug 2026, 20:38 | 4,484 | -7 |
| 21 Aug 2026, 03:35 | 4,491 | -5 |
| 17 Aug 2026, 18:15 | 4,496 | -3 |
| 14 Aug 2026, 19:46 | 4,499 | -7 |
| 11 Aug 2026, 19:46 | 4,506 | -1 |
| 8 Aug 2026, 18:31 | 4,507 | -2 |
| 7 Aug 2026, 19:48 | 4,509 | first reading |
Engagement
18 posts held, back to 12 April 2026 β the reader has not yet reached the start of this channelβs public history, so older posts may sit further back, unread. Read across 4 pages 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 18 posts for this entry, the most recent from 6 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
INDIAN PREMIER LEAGUE 2026 MATCH NO. 49 06 MAY 07:30PM HYDERABAD V/S PUNJAB MATCH WINNER π HYDERABAD πβοΈ ANJALI TIPS CRICKET BETTING ...πΉβοΈπ
π§π§ DELHI π§π§DONE AND DUSTED β€π₯ ALWAYS QUEEN MASTERMIND BOSS ππ¦π΄π₯
INDIAN PREMIER LEAGUE 2026 MATCH NO. 43 01 MAY 07:30PM RAJASTHAN V/S DELHI MATCH WINNER π DELHI πβοΈ ANJALI TIPS CRICKET BETTING ...πΉβοΈπ
π¨πΌ GUJARAT π¨πΌDONE AND DUSTED β€π₯ ALWAYS QUEEN MASTERMIND BOSS ππ¦π΄π₯
INDIAN PREMIER LEAGUE 2026 MATCH NO. 42 30 APR 07:30PM BANGALORE V/S GUJARAT MATCH WINNER π GUJARAT πβοΈ ANJALI TIPS CRICKET BETTING ...πΉβοΈπ
π΅π¬ BANGALORE π΅π¬DONE AND DUSTED β€π₯ ALWAYS QUEEN MASTERMIND BOSS ππ¦π΄π₯
INDIAN PREMIER LEAGUE 2026 MATCH NO. 34 24 APR 07:30PM BANGALORE V/S GUJARAT MATCH WINNER π BANGALORE πβοΈ ANJALI TIPS CRICKET BETTING ...πΉβοΈπ
π²π° HYDERABAD π²π°DONE AND DUSTED β€π₯ ALWAYS QUEEN MASTERMIND BOSS ππ¦π΄π₯
INDIAN PREMIER LEAGUE 2026 MATCH NO. 27 18 APR 07:30PM CHENNAI V/S HYDERABAD MATCH WINNER π HYDERABAD πβοΈ ANJALI TIPS CRICKET BETTING ...πΉβοΈπ
π§π§ DELHI π§π§DONE AND DUSTED β€π₯ ALWAYS QUEEN MASTERMIND BOSS ππ¦π΄π₯
INDIAN PREMIER LEAGUE 2026 MATCH NO. 26 18 APR 03:30PM BANGALORE V/S DELHI MATCH WINNER π DELHI πβοΈ ANJALI TIPS CRICKET BETTING ...πΉβοΈπ
Showing the 12 most recent of 18 posts we hold for @Anjali_tips_cricket_betting. 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.
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.
@INDIANBADSHAH Β· 47,404
Telegram ranks this channel #9 of 49 here β alongside 48 others β read 25 August 2026
@sidragaming_Nomankhan Β· 50,860
Telegram ranks this channel #24 of 58 here β alongside 57 others β read 26 August 2026
@Cricket_Father_CricketFather Β· 25,589
Telegram ranks this channel #36 of 48 here β alongside 47 others β read 14 September 2026
@Examsresultinfo Β· 27,802
Telegram ranks this channel #41 of 49 here β alongside 48 others β read 10 September 2026
This channel appears in 4 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 26 September 2026 β this entry's latest reading, not the date you are reading this.
βANJALI TIPS ... β€ππ CRICKET BETTINGβ (@Anjali_tips_cricket_betting), 4,419 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/Anjali_tips_cricket_betting.
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.