Telegram RegisterThe public register of Telegram
Telegram profile photo for Kabir Khan {AnalysT}

Channel

Kabir Khan {AnalysT}

@fixerkabir

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

162subscribers

-4 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001377485230
TypeChannel
Username@fixerkabir
CreatedBetween 1 March 2018 and 27 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/fixerkabir

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

1621661647 August 2026 — 166 subscribers8 August 2026 — 166 subscribers30 August 2026 — 165 subscribers8 September 2026 — 163 subscribers17 September 2026 — 162 subscribers7 August 202617 September 2026
5 measurements spanning 41 days, net -4. 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 161–167 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 06:00162-1
8 Sept 2026, 14:55163-2
30 Aug 2026, 08:55165-1
8 Aug 2026, 16:00166no change
7 Aug 2026, 03:00166first reading

Engagement

20 posts held, back to 27 September 2020 — the 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 14 September 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

14 Sept 2021, 17:48 UTCviews —

The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 7 days, that account will self-destruct and this channel will no longer have an owner.

11 Oct 2020, 16:53 UTC≈2,930 viewsread 8 August 2026

25p mumbai khao.... DELHI CAPITAL win karo..❤️❤️

10 Oct 2020, 15:34 UTC≈1,410 viewsread 8 August 2026

Ipl 😂😂✔️✔️ Aaise Fixing 10 sal mein nahi dekha ✔️✔️

30 Sept 2020, 15:59 UTC≈2,460 viewsread 8 August 2026

Target 175 for RAJSTHAN ROYALS Chase ho jayega baithe raho RAJSTHAN ke sath.. Best of luck ✌️

30 Sept 2020, 14:02 UTC≈2,500 viewsread 8 August 2026

*Indian premier league 2020* *RAJSTHAN ROYALS* Vs *KOLKATA KNIGHT RIDERS* Winner- RAJSTHAN ROYAL 💯✔️ Open rate *KKR* 92p half limit use karo.. *RAJSTHAN* win karo..half limit running match m *KKR* under 50p pe use karna *RAJSTHAN* karna..👍 Each n every rate only only *RAJSTHAN ROYALS* will win this match ✌️ *Kabir khan*

29 Sept 2020, 16:58 UTC≈2,930 viewsread 8 August 2026

30p SRH fev h jitna kha sakte ho khao.. DELHI will win ❤️

29 Sept 2020, 15:54 UTC894 viewsread 8 August 2026

Target 163 for DELHI CAPITALS Score chase ho jayega...match m SRH low lagna pasand h..but match DELHI CAPITALS win karega non cutting 👍

29 Sept 2020, 10:38 UTC≈2,690 viewsread 8 August 2026

*Indian premier league 2020* *Delhi capital* *Vs* *Sunrise Hyderabad* Winner- DELHI CAPITALS 💯✔️ Open rate 90P DELHI fev ... Wait SRH ke fev aane ka..SRH ko har bhaw m khana.. SRH under 30p extra limit use karo or DELHI CAPITALS win karo..👍 99% JACKPOT Each n every rate only only *DELHI CAPITAL* will win this match ✌️ *Kabir khan*

29 Sept 2020, 02:44 UTC633 viewsread 8 August 2026
Forwarded from @SupermanLiveLine

WINNER ;- 🇳🇬 BANGALORE 🇳🇬 ✔️✔️

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

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

“Kabir Khan {AnalysT}” (@fixerkabir), 162 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/fixerkabir.

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.