Telegram RegisterThe public register of Telegram
Telegram profile photo for Sevdiyorovna's blog ❤️

Channel

Sevdiyorovna's blog ❤️

@Sevdiyorovnas_blog

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

102subscribers

-16 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-1002363143159
TypeChannel
Username@Sevdiyorovnas_blog
Created27 October 2024measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live16 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/Sevdiyorovnas_blog

Growth

1021181107 August 2026 — 118 subscribers7 August 2026 — 117 subscribers9 August 2026 — 117 subscribers14 August 2026 — 113 subscribers23 August 2026 — 111 subscribers29 August 2026 — 109 subscribers8 September 2026 — 106 subscribers16 September 2026 — 102 subscribers7 August 202616 September 2026
8 measurements spanning 40 days, net -16. 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 100–120 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 16:36102-4
8 Sept 2026, 03:58106-3
29 Aug 2026, 08:47109-2
23 Aug 2026, 02:24111-2
14 Aug 2026, 17:07113-4
9 Aug 2026, 05:02117no change
7 Aug 2026, 21:41117-1
7 Aug 2026, 14:16118first reading

Engagement

4 posts held, back to 27 October 2024the 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 4 posts for this entry, the most recent from 15 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
6s
Average length
6s

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

236 reactions across 3 posts, in 15 distinct kinds. The most used accounts for 32.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍7732.6%
5523.3%
❤‍🔥208.47%
🥰208.47%
👏145.93%
🕊114.66%
🔥104.24%
💘62.54%
🖕62.54%
🥴52.12%
31.27%
🎉31.27%
💯20.847%
😱20.847%
🤗20.847%

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 4 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 236 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 4 most recent posts we hold, published 27 October 2024 to 15 February 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

15 Feb 2026, 17:34 UTC≈2,170 views31 reactionsread 9 August 2026
Photo

Õzbekistondagi ayol qizlar rivojlanishi uchun ❤️💫 https://t.me/+oXQ5fSLDaysyMmQy

11🥰8👏4🔥32😱2🎉1

19 Mar 2025, 19:45 UTC≈6,740 views81 reactionsread 9 August 2026

Asosiy kanalim linki bu eslatib oʻtaman soʻrov yuborsangiz qabul qilinasiz. Rivojlanishni istagan katta yutuqlarga erishishni istagan oʻz ustida ishlaydigan maqsadlari uchun harakat qiladigan insonlar uchun kanal faqatgina❤️

👍33❤‍🔥2015🥰3🎉2💘2💯2🔥2

27 Oct 2024, 12:51 UTC≈9,500 views124 reactionsread 9 August 2026

Õzbekistondagi ayol qizlar rivojlanishi uchun ❤️💫 https://t.me/+oXQ5fSLDaysyMmQy

👍4429🕊11👏10🥰9🔥5🥴5💘4

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

“Sevdiyorovna's blog ❤️” (@Sevdiyorovnas_blog), 102 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Sevdiyorovnas_blog.

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.