Telegram RegisterThe public register of Telegram
Telegram profile photo for IPL_TOSS_MATCH2024

Supergroup

IPL_TOSS_MATCH2024

@IPL_TOSS_MATCH_REPORT5

Has discussion group

On this record: Topic · Growth · Engagement · Cite this entry

3,535members

-320 since we began measuring on 7 August 2026

32 online right now

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

Register entry

Telegram ID-1001933642961
TypeSupergroup
Username@IPL_TOSS_MATCH_REPORT5
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 September 2026
Last confirmed live3 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/IPL_TOSS_MATCH_REPORT5

Topic

Sports — 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 14 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 the other topics.

Growth

3,5353,8553,6957 August 2026 — 3,855 members10 August 2026 — 3,841 members14 August 2026 — 3,821 members17 August 2026 — 3,810 members20 August 2026 — 3,801 members23 August 2026 — 3,783 members26 August 2026 — 3,776 members30 August 2026 — 3,770 members2 September 2026 — 3,758 members6 September 2026 — 3,758 members7 September 2026 — 3,743 members11 September 2026 — 3,717 members16 September 2026 — 3,708 members29 September 2026 — 3,667 members6 October 2026 — 3,642 members12 October 2026 — 3,616 members15 October 2026 — 3,595 members19 October 2026 — 3,585 members22 October 2026 — 3,573 members25 October 2026 — 3,564 members28 October 2026 — 3,549 members31 October 2026 — 3,540 members3 November 2026 — 3,535 members7 August 20263 November 2026
23 measurements spanning 87 days, net -320. 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 3,487–3,903 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 23
Measured (UTC)MembersChange
3 Nov 2026, 05:473,535-5
31 Oct 2026, 07:553,540-9
28 Oct 2026, 13:373,549-15
25 Oct 2026, 14:583,564-9
22 Oct 2026, 08:353,573-12
19 Oct 2026, 05:473,585-10
15 Oct 2026, 23:273,595-21
12 Oct 2026, 18:503,616-26
6 Oct 2026, 09:413,642-25
29 Sept 2026, 10:003,667-41
16 Sept 2026, 00:393,708-9
11 Sept 2026, 21:173,717-26
7 Sept 2026, 05:553,743-15
6 Sept 2026, 22:433,758no change
2 Sept 2026, 02:133,758-12
30 Aug 2026, 00:243,770-6
26 Aug 2026, 16:123,776-7
23 Aug 2026, 16:073,783-18
20 Aug 2026, 08:173,801-9
17 Aug 2026, 13:033,810first 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“IPL_TOSS_MATCH2024” (@IPL_TOSS_MATCH_REPORT5), 3,535 members as measured 3 November 2026. Telegram Register, tgregister.com/channel/IPL_TOSS_MATCH_REPORT5.

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.