Channel
@muhabbatmasofasi
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
25subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001427965519 |
|---|---|
| Type | Channel |
| Username | @muhabbatmasofasi |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 3 times, most recently 14 September 2026 |
| On Telegram | t.me/muhabbatmasofasi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 01:57 | 25 | -1 |
| 23 Aug 2026, 00:15 | 26 | -1 |
| 14 Aug 2026, 21:37 | 27 | +2 |
| 11 Aug 2026, 09:15 | 25 | no change |
| 6 Aug 2026, 21:32 | 25 | first reading |
19 posts held, back to 16 December 2025 — 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 19 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
59 reactions across 19 posts, in 25 distinct kinds. The most used accounts for 10.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5391054099674317443 | 6 | 10.2% | |
| custom 5273893142800638358 | 5 | 8.47% | |
| custom 5339086713379625821 | 5 | 8.47% | |
| custom 5390972658504450702 | 5 | 8.47% | |
| 🤩 | 4 | 6.78% | |
| ☃ | 3 | 5.08% | |
| ❤ | 3 | 5.08% | |
| ❤🔥 | 3 | 5.08% | |
| 🔥 | 3 | 5.08% | |
| 🕊 | 3 | 5.08% | |
| custom 5359807774509248647 | 2 | 3.39% | |
| custom 5386421350380351231 | 2 | 3.39% | |
| 🐳 | 2 | 3.39% | |
| 😢 | 2 | 3.39% | |
| custom 5210726994353863536 | 1 | 1.69% | |
| custom 5460993759439236880 | 1 | 1.69% | |
| custom 5461167482276432037 | 1 | 1.69% | |
| 🍾 | 1 | 1.69% | |
| 🎄 | 1 | 1.69% | |
| 🎉 | 1 | 1.69% | |
| 5 further kinds | 5 | 8.47% |
Custom emoji. 9 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 19 of the 19 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 59 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 16 December 2025 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.
Ne'matning odobi Sizga berilgan ne'matni unga yeta olmagan odamning oldida ko'z-ko'z qilmaslik ham o'sha ne'matning odobidir! "Sahobalardan maktublar"
custom 52738931428006383581custom 53909726585044507021custom 53910540996743174431
Video, posted without a caption
😢1
Video, posted without a caption
custom 52738931428006383581custom 53598077745092486471custom 54611674822764320371
File, posted without a caption
custom 53598077745092486471
Sticker, posted without a caption
❤1🔥1🕊1🤩1
🌈🌈🌈
👏1🔥1🤩1
Photo, posted without a caption
🐳2🕊1🤩1
Sticker, posted without a caption
❤1❤🔥1😍1
🩵
😐1😢1🙏1
Video, posted without a caption
❤1❤🔥1🔥1
Assalomu alaykum 😊
🎉1🕊1🤩1
Sticker, posted without a caption
custom 53390867133796258211custom 53909726585044507021custom 53910540996743174431
Showing the 12 most recent of 19 posts we hold for @muhabbatmasofasi. 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.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“Muhabbat masofasi ❤️❤️❤️” (@muhabbatmasofasi), 25 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/muhabbatmasofasi.
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.