Telegram RegisterThe public register of Telegram
Telegram profile photo for Ozodbek Omonov

Channel

Ozodbek Omonov

@ozod_vi

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

7subscribers

-2 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-1002026395046
TypeChannel
Username@ozod_vi
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live18 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/ozod_vi

Growth

7987 August 2026 — 9 subscribers12 August 2026 — 9 subscribers18 September 2026 — 7 subscribers7 August 202618 September 2026
3 measurements spanning 42 days, net -2. 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 7–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 05:557-2
12 Aug 2026, 11:469no change
7 Aug 2026, 12:219first reading

Engagement

16 posts held, back to 23 May 2026the 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 16 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
24s
Average length
24s

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.

Reaction mix

27 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 37.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1037.0%
custom 5454169404298260342829.6%
414.8%
👍27.41%
custom 540681335688555047613.70%
custom 545403155302792152413.70%
🕊13.70%

Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 11 of the 16 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 27 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 23 May 2026 to 24 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

24 Jul 2026, 10:24 UTC34 views3 reactionsread 12 August 2026
Photo

3-kurs tugadi😅

🔥2custom 54068133568855504761

22 Jul 2026, 23:01 UTC34 views1 reactionsread 12 August 2026
Voice message

Хаммасни тушунтиришга харакат килдим, кеин тушундим; хамма ешитишга таййор емас.

🔥1

29 Jun 2026, 05:39 UTC58 views2 reactionsread 12 August 2026

Hech bir ma'noni anglatmaydigan so‘zlardan ko‘ra.. Hamma narsani so‘zlaydigan, jimliklar afzal.

custom 54540315530279215241custom 54541694042982603421

29 Jun 2026, 05:39 UTC60 views2 reactionsread 12 August 2026

Alloh tomonidan keladigan har bir hayrni kuting, U kechikishi mumkin, ammo juda go‘zal bo‘ladi..!

custom 54541694042982603422

Showing the 12 most recent of 16 posts we hold for @ozod_vi. 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Ozodbek Omonov” (@ozod_vi), 7 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ozod_vi.

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.