Telegram RegisterThe public register of Telegram
Telegram profile photo for Настя в режиме «держусь»

Channel

Настя в режиме «держусь»

@blinvzloslayazizn

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

155subscribers

+4 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002770059765
TypeChannel
Username@blinvzloslayazizn
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/blinvzloslayazizn

Growth

1511551537 August 2026 — 151 subscribers8 August 2026 — 151 subscribers15 August 2026 — 154 subscribers28 August 2026 — 153 subscribers7 September 2026 — 154 subscribers15 September 2026 — 155 subscribers7 August 202615 September 2026
6 measurements spanning 38 days, net +4. 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 150–156 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 02:18155+1
7 Sept 2026, 11:37154+1
28 Aug 2026, 21:44153-1
15 Aug 2026, 09:56154+3
8 Aug 2026, 19:45151no change
7 Aug 2026, 16:59151first reading

Engagement

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

What this channel posts

Video runtime
29s
Average length
15s

Measured directly from 2 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.

Reaction mix

44 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 63.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2863.6%
custom 59969161450917759601022.7%
custom 5357579953497983889511.4%
👍12.27%

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

Measured over the 15 most recent posts we hold, published 18 July 2026 to 8 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

8 Aug 2026, 13:17 UTC13 viewsread 8 August 2026

Может тут есть кто работает в страховой ? Нужно осаго оформить 👀

8 Aug 2026, 06:10 UTC20 views4 reactionsread 8 August 2026
Photo

Доброе утро,котики Это я шараебилась по какому-то парку в 7 утра и пила какую-то сцанину с заправки. У меня все. Всем чудесного дня

4

7 Aug 2026, 16:14 UTC23 views4 reactionsread 8 August 2026
Photo

Такая милота в кофейне

4

7 Aug 2026, 16:13 UTC23 views3 reactionsread 8 August 2026
Video

Работаю работу ) Если вдруг кто в поиске то велком) Питер,приморский район 👀

3

27 Jul 2026, 09:55 UTC207 views15 reactionsread 8 August 2026
Photo

Если ваш товар пострадал на Wb Я готова бесплатно сделать несколько сайтов для тех, кто хочет перейти на прямые продажи и начать работать с клиентами без посредников. Если вы давно думали о своем сайте, но откладывали — это отличный шанс начать. Напишите мне в личные сообщения, коротко расскажите о своем товаре. Выберу несколько проектов и сделаю сайты бесплатно.

6custom 59969161450917759605custom 53575799534979838894

27 Jul 2026, 09:29 UTC48 views5 reactionsread 8 August 2026

Posted without readable text

3👍1custom 59969161450917759601

25 Jul 2026, 13:04 UTC44 viewsread 8 August 2026

Во всем мире хаос Тем временем в Беларуси 😂

25 Jul 2026, 13:04 UTC43 viewsread 8 August 2026
Forwarded from @ryanrunVideo

Беларусы начали взвешивать пивозавров. Любители пенного могут узнать свой вес в бутылках «жидкого золота». Такие весы установили в Бресте, они переводят вес в пиво или драники. Выезжаем.

25 Jul 2026, 11:21 UTC44 views4 reactionsread 8 August 2026
Photo

Немного начал уходить живот Я счастлива но все же не так стремительно как хотелось бы

3custom 53575799534979838891

25 Jul 2026, 11:20 UTC44 views1 reactionsread 8 August 2026

В итоге никуда я не пошла , проснулась в 4 утра с тревожностью, отменила смену

1

24 Jul 2026, 13:37 UTC46 viewsread 8 August 2026

Завтра иду на подработку через вентру На всякий случай сейчас нужно напрячься и поработать

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“Настя в режиме «держусь»” (@blinvzloslayazizn), 155 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/blinvzloslayazizn.

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.