✈️
custom 546529266092527789710🕊3custom 53936072902280677502custom 52313567702485732101custom 54655818281884165641

Channel
@misyyan
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
108subscribers
-2 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001982489979 |
|---|---|
| Type | Channel |
| Username | @misyyan |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/misyyan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 00:15 | 108 | -1 |
| 18 Aug 2026, 01:52 | 109 | -1 |
| 10 Aug 2026, 16:15 | 110 | no change |
| 10 Aug 2026, 16:01 | 110 | first reading |
6 posts held, back to 4 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 6 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 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.
107 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 35.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5465292660925277897 | 38 | 35.5% | |
| custom 5465581828188416564 | 30 | 28.0% | |
| 🕊 | 26 | 24.3% | |
| custom 5231356770248573210 | 11 | 10.3% | |
| custom 5393607290228067750 | 2 | 1.87% |
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 6 of the 6 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 107 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 4 June 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.
✈️
custom 546529266092527789710🕊3custom 53936072902280677502custom 52313567702485732101custom 54655818281884165641
Photo, posted without a caption
🕊6custom 54655818281884165645custom 52313567702485732102custom 54652926609252778971
Photo, posted without a caption
custom 54652926609252778977🕊1custom 54655818281884165641
«любовь никогда не перестает»
custom 54655818281884165649custom 52313567702485732105🕊2custom 54652926609252778972
Стоит просто довериться плану Творца.
custom 546529266092527789714custom 54655818281884165648🕊5custom 52313567702485732102
Церковь Сурб Хач📍 Армянская церковь в Ростове-на-Дону, одна из сохранившихся построек ранее существовавшего монастыря.
🕊9custom 54655818281884165646custom 54652926609252778974custom 52313567702485732101
Showing the 6 most recent of 6 posts we hold for @misyyan. 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.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“misyan” (@misyyan), 108 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/misyyan.
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.