Channel
@tasirli_ohang
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
94subscribers
-9 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002540445414 |
|---|---|
| Type | Channel |
| Username | @tasirli_ohang |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/tasirli_ohang |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 01:17 | 94 | -4 |
| 1 Sept 2026, 07:28 | 98 | -2 |
| 26 Aug 2026, 03:16 | 100 | -2 |
| 18 Aug 2026, 05:22 | 102 | -1 |
| 11 Aug 2026, 21:45 | 103 | no change |
| 11 Aug 2026, 21:33 | 103 | first reading |
20 posts held, back to 22 June 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 20 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 6 videos 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.
77 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 36.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5447197542800451036 | 28 | 36.4% | |
| ❤ | 22 | 28.6% | |
| custom 5445363892412768753 | 15 | 19.5% | |
| custom 5190660975866437599 | 5 | 6.49% | |
| 🔥 | 4 | 5.19% | |
| custom 5447346775734119855 | 2 | 2.60% | |
| ❤🔥 | 1 | 1.30% |
Custom emoji. 4 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 20 of the 20 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 77 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 22 June 2026 to 10 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.
Sogʻinch xatlaridan toʻlmoqda varoq Bu armon egasi bilmam kim ekan Alamdan qon boʻldim va yana biroq Bir baxtga yetolmagan kim ekan Qishsiz yuragini bogʻi soʻlgamday Men uchun sevgisi mehri oʻlganday Uningche osmonda oyi toʻlganday Bir baxtga yetolmagan kim ekan Sharobu tutundan olmam alamim Toʻxtamay sher yozdim sindi qalamim Oʻzgasiga kelin boʻlar bugun sanamim Bir baxtga yetolmagan kim ekan Hayotning nodon bol…
❤1🔥1
Poʻlat (((Elif••••❤️🩹
❤1
Yangisi chiqsinmi ❓ • • • Javob kutaman✅
❤3
❤️🩹••••••••🎶🚯
❤1🔥1
🫀☝️🏻ال صبر ✨
❤4
Sen bilan umrbod qolmoqchi edim, Yagonang, yolgʻizing boʻlmoqchi edim, Oʻlsam ham sen bilan oʻlmoqchi edim, Orzuni men qildim boshqalar yetdi! Qoʻl ushlashib birga yurmoqchi edim, Tillodan saroylar qurmoqchi edim, Kulsang, birgalashib kulmoqchi edim, Orzuni men qildim boshqalar yetdi! Koʻzingda koʻzimni koʻrmoqchi edim, "Baxtlimisan" deya soʻrmoqchi edim, Ishq ila sururga toʻlmoqchi edim, Orzuni men qildim boshqala…
custom 54471975428004510364❤1🔥1
🌧🔋
custom 54471975428004510363
Yillar zaboniga tutib bir tugun Oy kunlar fasillar yiroqlab ketdi Unutishga yurak koʻnibdi bugun Seni unutmoqqa madorim yetdi Hasratlardan chekindim Boʻldim butkul men taslim Soyang koʻrsam bekindim Baxtsizlarda bordayin qastim Chekinarman albatta Deb uylarsan sen latta Soʻngi bora bir martta Unutmoqqa madorim yetdi Nega axir bormasman Yonginangda qolmasman Ishonchimdan tondirding Boshqa ishqda yonmasman Jabr c…
custom 54471975428004510362custom 54453638924127687531
💯😅
custom 54453638924127687532custom 54471975428004510361
божалар - мухаббат
custom 54471975428004510364custom 54453638924127687531
🥺❤️🩹•••••••🎧
custom 54453638924127687532custom 54471975428004510362
🌝❤️🔥 Koʻrib koʻzlar lolmikam Yaraqlaydi koʻzchasi Sevmay iloj bormikan Oy momoning qizchasi 🌝 Sevgimdanku man hayron Oppoqqina yuzchasi Mingta oʻgʻlon zormikan Oy momoning qizchasi 🌝 Jonim bersam kam senga Muloyimdir soʻzchasi Sevging aytgin sen menga Oy momoning qizchasi 🌝 Koʻzim yumsam hayolda Aylanadi boʻychasi Meni ado qilganda Oy momoning qizchasi 🌝 Qoʻlin tutsam hayronman Jimjiloqday qoʻlchasi Menga juda …
❤4custom 54471975428004510362🔥1custom 54453638924127687531
Showing the 12 most recent of 20 posts we hold for @tasirli_ohang. 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.
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.
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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“❤️🩹 𝗦𝗵𝗲ʼ𝗿𝗶𝘆 𝘁𝗼ʻ𝗽𝗹𝗮𝗺𝗹𝗮𝗿𝗶𝗺 🖤” (@tasirli_ohang), 94 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/tasirli_ohang.
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.