Channel
@semyvosem
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
872subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001446542208 |
|---|---|
| Type | Channel |
| Username | @semyvosem |
| Created | Between 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 29 August 2026 |
| On Telegram | t.me/semyvosem |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 09:03 | 872 | -1 |
| 15 Aug 2026, 04:38 | 873 | -3 |
| 7 Aug 2026, 12:36 | 876 | +1 |
| 6 Aug 2026, 16:11 | 875 | no change |
| 6 Aug 2026, 16:09 | 875 | first reading |
20 posts held, back to 10 February 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 pageof 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 16 July 2026. An engagement rate over an empty window would be a number about nothing.
120 reactions across 20 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5391327053435925994 | 120 | 100.0% |
Custom emoji. One row above is a 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 count beside it isTelegram’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 120reactions 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 10 February 2026 to 16 July 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 53913270534359259944
пережить можно все, нельзя после этого остаться прежним
custom 53913270534359259944
если тебе станет грустно, помни, что у тебя есть я, хорошо? может, я и не так уж много значу, но я буду рядом с тобой.
custom 53913270534359259944
Photo, posted without a caption
custom 53913270534359259944
возьми из моей радости столько, сколько пожелаешь, пока не будет сиять твое лицо. будь счастлива сначала ты, затем, посредством тебя, буду счастлив я
custom 53913270534359259946
я лишь остался твоим забытым воспоминанием
custom 53913270534359259944
Иногда Он допускает раны, чтобы спасти тебя от того, что могло бы уничтожить. Настанет день, и как бы странно это сейчас для тебя не звучало, но ты поблагодаришь Его за то, что Он уберег тебя. После любой боли Он даст тебе утешение, и после тонны слез - дни тишины и тихой радости
custom 53913270534359259948
о Аллаh, храни ее сердце и даруй ей счастье, где бы она ни была
custom 53913270534359259947
но рядом ты, и мир становится не таким уж и невыносимым.
custom 53913270534359259945
самый печальный конец - это когда тебе пришлось расстаться с тем, кого ты все ещё любишь всем сердцем
custom 53913270534359259946
«и если можно было бы все отмотать и не болеть - я бы заново тобою заболел, чтобы умереть»
custom 53913270534359259946
Ты был единственным, к кому я хотела уйти, оставив весь мир где-то там, за спиной
custom 53913270534359259946
Signed •
Showing the 12 most recent of 20 posts we hold for @semyvosem. 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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“ㅤsemyvosem” (@semyvosem), 872 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/semyvosem.
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.