Telegram RegisterThe public register of Telegram
Telegram profile photo for Ibroxim Shox | Rasmiy kanal

Channel

Ibroxim Shox | Rasmiy kanal

@ibroximshox

Has discussion group

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

1,032subscribers

-80 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1001322739522
TypeChannel
Username@ibroximshox
DescriptionАссалом алекум ! Иброхим Шох Шахсий каналига хуш келибсиз 👇🏿 Каналимизга обуна бўлинг...
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 October 2026
Last confirmed live11 October 2026
Measurements held14
On Telegramt.me/ibroximshox

Topic

Personal blog — 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 8 October 2026 and assigned it the closest of 31 fixed categories, at 68% 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

1,0321,1121,07214 August 2026 — 1,112 subscribers15 August 2026 — 1,098 subscribers18 August 2026 — 1,090 subscribers21 August 2026 — 1,089 subscribers25 August 2026 — 1,084 subscribers28 August 2026 — 1,081 subscribers31 August 2026 — 1,072 subscribers3 September 2026 — 1,068 subscribers9 September 2026 — 1,061 subscribers13 September 2026 — 1,054 subscribers18 September 2026 — 1,051 subscribers26 September 2026 — 1,039 subscribers5 October 2026 — 1,032 subscribers8 October 2026 — 1,032 subscribers14 August 20268 October 2026
14 measurements spanning 56 days, net -80. 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 1,020–1,124 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 18:151,032no change
5 Oct 2026, 09:381,032-7
26 Sept 2026, 22:421,039-12
18 Sept 2026, 01:021,051-3
13 Sept 2026, 13:401,054-7
9 Sept 2026, 08:381,061-7
3 Sept 2026, 14:571,068-4
31 Aug 2026, 02:121,072-9
28 Aug 2026, 04:081,081-3
25 Aug 2026, 05:021,084-5
21 Aug 2026, 23:271,089-1
18 Aug 2026, 18:141,090-8
15 Aug 2026, 10:451,098-14
14 Aug 2026, 05:491,112first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Ibroxim Shox | Rasmiy kanal” (@ibroximshox), 1,032 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/ibroximshox.

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.