Telegram RegisterThe public register of Telegram
Telegram profile photo for Khan (Fixer) IPL💸

Channel

Khan (Fixer) IPL💸

@Khan_Fixxer

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry

2,283subscribers

-30 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001448715534
TypeChannel
Username@Khan_Fixxer
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 November 2026
Measurements held20
Confirmed unchanged2 times, most recently 19 November 2026
On Telegramt.me/Khan_Fixxer

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 16 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

2,2832,3132,2987 August 2026 — 2,313 subscribers7 August 2026 — 2,313 subscribers10 August 2026 — 2,312 subscribers13 August 2026 — 2,311 subscribers17 August 2026 — 2,310 subscribers26 August 2026 — 2,305 subscribers1 September 2026 — 2,304 subscribers4 September 2026 — 2,303 subscribers10 September 2026 — 2,302 subscribers13 September 2026 — 2,300 subscribers27 September 2026 — 2,298 subscribers5 October 2026 — 2,297 subscribers11 October 2026 — 2,295 subscribers15 October 2026 — 2,293 subscribers18 October 2026 — 2,292 subscribers21 October 2026 — 2,289 subscribers27 October 2026 — 2,287 subscribers3 November 2026 — 2,286 subscribers9 November 2026 — 2,284 subscribers14 November 2026 — 2,283 subscribers7 August 202614 November 2026
20 measurements spanning 99 days, net -30. 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,279–2,318 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Nov 2026, 07:482,283-1
9 Nov 2026, 17:442,284-2
3 Nov 2026, 03:072,286-1
27 Oct 2026, 18:152,287-2
21 Oct 2026, 15:482,289-3
18 Oct 2026, 06:212,292-1
15 Oct 2026, 03:482,293-2
11 Oct 2026, 16:592,295-2
5 Oct 2026, 08:212,297-1
27 Sept 2026, 08:172,298-2
13 Sept 2026, 13:402,300-2
10 Sept 2026, 02:192,302-1
4 Sept 2026, 18:422,303-1
1 Sept 2026, 10:572,304-1
26 Aug 2026, 23:462,305-5
17 Aug 2026, 11:282,310-1
13 Aug 2026, 17:542,311-1
10 Aug 2026, 17:212,312-1
7 Aug 2026, 01:302,313no change
7 Aug 2026, 01:192,313first reading

Engagement

20 posts held, back to 29 May 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 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 20 posts for this entry, the most recent from 29 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
28s
Average length
28s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

29 May 2026, 16:49 UTC51 viewsread 7 August 2026

IPL 2026😍 Final Match Winner🏆RCB🏆💯 Winner🏆RCB🏆💯 5x Limit Se Khelna Ye Match... Non-Cutting RCB:- 👍 T.V Band Report... Telegram Tod Report... Bookie Khatam Report... #Khan_Fixer😍

3 Jun 2025, 17:40 UTC255 viewsread 7 August 2026

Kisi ka Bab Bhi (RCB) ko nahi Hara Payaga Bat Khatam....👍

30 May 2025, 14:56 UTC294 viewsread 7 August 2026

IPL 2025😍 Final Match Winner🏆RCB🏆💯 Winner🏆RCB🏆💯 5x Limit Se Khelna Ye Match... Non-Cutting RCB:- 👍 T.V Band Report... Telegram Tod Report... Bookie Khatam Report... #Khan_Fixer😍

31 Mar 2025, 14:13 UTC367 viewsread 7 August 2026
Photo

M U M B A I ❤️ W I N 💯 Sure Match 💯 https://t.me/joinchat/AAAAAFZZpQ7mxSWWOERpIA

18 May 2024, 14:32 UTC522 viewsread 7 August 2026
Photo

B A N G A L O R E ❤️ W I N 💯 Sure Match 💯 https://t.me/joinchat/AAAAAFZZpQ7mxSWWOERpIA

11 Apr 2024, 16:29 UTC634 viewsread 7 August 2026

M U M B A I ❤️ W I N 💯 Sure Match 💯 https://t.me/joinchat/AAAAAFZZpQ7mxSWWOERpIA

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

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

“Khan (Fixer) IPL💸” (@Khan_Fixxer), 2,283 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/Khan_Fixxer.

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.