Telegram RegisterThe public register of Telegram
Telegram profile photo for vs.sanechka

Channel

vs.sanechka

@vs_sanechk

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

692subscribers

-22 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001904388048
TypeChannel
Username@vs_sanechk
CreatedBetween 1 March 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live31 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/vs_sanechk

Growth

6927147038 August 2026 — 714 subscribers8 August 2026 — 714 subscribers9 August 2026 — 712 subscribers16 August 2026 — 707 subscribers24 August 2026 — 696 subscribers31 August 2026 — 692 subscribers8 August 202631 August 2026
6 measurements spanning 23 days, net -22. 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 689–717 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 19:06692-4
24 Aug 2026, 13:05696-11
16 Aug 2026, 07:56707-5
9 Aug 2026, 01:44712-2
8 Aug 2026, 07:20714no change
8 Aug 2026, 07:19714first reading

Engagement

16 posts held, back to 22 July 2026the 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 16 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

273 reactions across 15 posts, in 5 distinct kinds. The most used accounts for 41.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 537760226210325707311241.0%
custom 53773518655098996235018.3%
💘5018.3%
💅3412.5%
custom 5377346325002086977279.89%

Custom emoji. 3 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 15 of the 16 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 273 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 22 July 2026 to 7 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.

Recent posts

7 Aug 2026, 15:13 UTC141 views2 reactionsread 8 August 2026

Моя миииииилая мама 🫶

💘2

7 Aug 2026, 15:13 UTC141 views10 reactionsread 8 August 2026
Video message

Video message, posted without a caption

💅10

7 Aug 2026, 15:13 UTC139 views10 reactionsread 8 August 2026
Voice message

Voice message, posted without a caption

custom 537735186550989962310

7 Aug 2026, 14:21 UTC164 views13 reactionsread 8 August 2026
Photo

Сделала мою любимую укладку Хагрида, даже челка закололась красиво! Но как выйти с такой копной волос в +30 🤩 Все лето хожу с пучками, тк вообще нереально в жару с распущенными. Начала раз в два дня думать о каре, оно так и манит меня 🤩

💅13

6 Aug 2026, 19:10 UTC195 views10 reactionsread 8 August 2026

Резко захотелось что-то поменять… Последние разы после подобных мыслей появилась челка и я почти перестала снимать в тт 😊

custom 537760226210325707310

2 Aug 2026, 17:54 UTC357 views7 reactionsread 8 August 2026

Ой жесть, хотела сделать красиво, а получилось что-то странное 👀

custom 53773518655098996237

2 Aug 2026, 17:54 UTC361 views12 reactionsread 8 August 2026

Posted without readable text

custom 53776022621032570737💘5

1 Aug 2026, 18:10 UTC275 views23 reactionsread 8 August 2026
Photo

Вечера, когда меня не слышно и не видно 🙏

custom 537735186550989962321custom 53776022621032570732

1 Aug 2026, 15:04 UTC297 views36 reactionsread 8 August 2026
Photo

😡

custom 537760226210325707320💘10💅6

31 Jul 2026, 09:37 UTC293 views31 reactionsread 8 August 2026

Друзья, я решила идти в магистратуру в педагогический 😊 Плюсов пока не вижу, если только мое желание. Из минусов: моя семья от меня отказалась, а мама с тяжелым вздохом сказала «ну в семье не без урода». Я не понимаю, почему они так не любят пед….

custom 537760226210325707320custom 537734632500208697711

30 Jul 2026, 06:46 UTC331 views21 reactionsread 8 August 2026

Кто вообще придумал завтраки в маке…. А главное, ПОЧЕМУ нет нормального меню утром 😭 Моя нога вступила на Московскую землю и первым делом я хочу просто булку с говядиной, а не ваш ссанный тост с яйцом 🤩

custom 537734632500208697716💘5

25 Jul 2026, 08:28 UTC431 views26 reactionsread 8 August 2026

Мне приснился сон с четверга на пятницу: Ваня Дмитриенко сделал мне предложение, а моему парню дал денег на раскручивание команды по футболу «Спартак», чтобы он не обижался 🤩 Сон вещий? Или что это за мув был…. Я вообще не фанат Дмитриенко 🥲

custom 537760226210325707323custom 53773518655098996233

Showing the 12 most recent of 16 posts we hold for @vs_sanechk. 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.

Forward network

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.

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 31 August 2026 — this entry's latest reading, not the date you are reading this.

“vs.sanechka” (@vs_sanechk), 692 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/vs_sanechk.

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.