Telegram RegisterThe public register of Telegram
Telegram profile photo for Чёлка штегена

Channel

Чёлка штегена

@stena1992

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

23subscribers

-1 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-1001961980723
TypeChannel
Username@stena1992
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/stena1992

Growth

232423.57 August 2026 — 24 subscribers11 August 2026 — 24 subscribers22 August 2026 — 23 subscribers7 August 202622 August 2026
3 measurements spanning 15 days, net -1. 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 23–24 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 04:4823-1
11 Aug 2026, 11:1724no change
7 Aug 2026, 11:1524first reading

Engagement

20 posts held, back to 21 January 2025the 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 9 February 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
22s
Average length
11s

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

43 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 34.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1534.9%
😁1330.2%
👍818.6%
🔥49.30%
👏24.65%
🥰12.33%

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 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 43reactions 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 21 January 2025 to 9 February 2025, 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

9 Feb 2025, 18:59 UTC205 views5 reactionsread 11 August 2026
Photo

Фермин выйдет и решит исход матча

5

8 Feb 2025, 13:29 UTC188 views2 reactionsread 11 August 2026
Photo

Это началось Процесс необратим

👏2

6 Feb 2025, 21:05 UTC131 views3 reactionsread 11 August 2026

Если Ферран так ебёт бывший клуб, боюсь что будет с дочкой Энрике

👍2🥰1

1 Feb 2025, 22:22 UTC103 views4 reactionsread 11 August 2026
Photo

Муд болельщика барсы

3👍1

1 Feb 2025, 14:39 UTC110 views1 reactionsread 11 August 2026
Photo

Зимнее трансферное окно если не считать миллион аренд

😁1

31 Jan 2025, 18:33 UTC126 views2 reactionsread 11 August 2026
Video

Лапорта, когда узнал , что Ман Сити хочет купить Нико Гонсалеса

2

30 Jan 2025, 19:27 UTC124 views2 reactionsread 11 August 2026
Photo

Полгодика на родине , а потом и в барсу можно

👍2

29 Jan 2025, 18:51 UTC73 views1 reactionsread 11 August 2026
Photo

Войцех сегодня без привозов

😁1

27 Jan 2025, 14:13 UTC103 views4 reactionsread 11 August 2026
Photo

- Ещё один миллион блядских фолов и я выиграю это чёртову Ла лигу

🔥4

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

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

“Чёлка штегена” (@stena1992), 23 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/stena1992.

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.