6 measurements spanning 32 days, net +182. 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 676–916 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
7 Sept 2026, 18:41
888
+182
30 Aug 2026, 11:54
706
-3
24 Aug 2026, 12:33
709
+5
15 Aug 2026, 19:54
704
-2
7 Aug 2026, 06:32
706
no change
7 Aug 2026, 06:27
706
first reading
Engagement
3 posts held, back to 16 July 2026 — 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 3 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
16 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 87.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
14
87.5%
🎉
1
6.25%
🔥
1
6.25%
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 3 of the 3 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 16 July 2026 to 4 August 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.
🎉 Urganch davlat tibbiyot instituti professor-o‘qituvchisi va talabalari Xitoydagi xalqaro amaliyot dasturini muvaffaqiyatli yakunlab, Vatanga qaytdilar. 🇺🇿🤝🇨🇳
Shenchjen universiteti qoshidagi 4-klinikada o‘tkazilgan yozgi amaliyot davomida ishtirokchilar zamonaviy tibbiyot va innovatsion yondashuvlar bo‘yicha amaliy tajriba orttirdilar.
🏅 Dastur yakunida professor-o‘qituvchi va talabalar xalqaro sertifikatlar bila…
🇺🇿🇰🇬 2026-yil 28–29-iyul kunlari Qirg‘iziston Respublikasida III O‘zbekiston–Qirg‘iziston oliy ta’lim muassasalari rektorlari forumi bo‘lib o‘tdi. Mazkur nufuzli forumda Urganch davlat tibbiyot instituti rektori Ruzibayev Rashid Yusupovich ham ishtirok etdi.
🤝 Forum doirasida Urganch davlat tibbiyot instituti hamda Bishkek shahridagi I.K. Axunbayev nomidagi Qirg‘iz davlat tibbiyot akademiyasi o‘rtasida hamkorlikni y…
👍Urganch davlat tibbiyot instituti talabalari Xitoyda yozgi xalqaro amaliyot o‘tamoqdalar
Urganch davlat tibbiyot institutining 1- va 2-bosqich talabalari Xitoy Xalq Respublikasidagi Shinjon tibbiyot universiteti qoshidagi 4-klinikada xalq tabobati yo‘nalishi bo‘yicha yozgi amaliyotda ishtirok etmoqdalar.
Mazkur amaliyot professor Bobojonov Xudoynazar Rajapovich rahbarligida tashkil etilgan bo‘lib, unda 30 nafar ta…
👍2🎉1🔥1
Showing the 3 most recent of 3 posts we hold for @Rashid_Ruzibayev. 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
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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 7 September 2026 — this
entry's latest reading, not the date you are reading this.
“Ruzibayev Rashid Yusupovich (rasmiy kanal)” (@Rashid_Ruzibayev), 888 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/Rashid_Ruzibayev.
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.
