Telegram RegisterThe public register of Telegram
Telegram profile photo for Хельхейм | рест

Channel

Хельхейм | рест

@HelheimSteym

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

123subscribers

-5 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002093175846
TypeChannel
Username@HelheimSteym
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live2 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/HelheimSteym

Growth

123128125.510 August 2026 — 128 subscribers10 August 2026 — 128 subscribers19 August 2026 — 126 subscribers26 August 2026 — 125 subscribers2 September 2026 — 123 subscribers10 August 20262 September 2026
5 measurements spanning 23 days, net -5. 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 122–129 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 13:17123-2
26 Aug 2026, 10:44125-1
19 Aug 2026, 07:27126-2
10 Aug 2026, 16:30128no change
10 Aug 2026, 16:17128first reading

Engagement

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

Reaction mix

54 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 22.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👾1222.2%
💋1018.5%
916.7%
💔916.7%
custom 523811912753666256747.41%
🕊47.41%
custom 525587826754980404235.56%
😨35.56%

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 7 of the 13 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 54 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 28 June 2026 to 6 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

6 Aug 2026, 06:56 UTC94 views3 reactionsread 10 August 2026

Мне только что черный кот дорогу перебежал. Посмеялся про себя, думаю, ну яж не суеверный, какая неудача ожидать меня может? И ХОБА нахуй, СИРЕНА. Кот, я все понимаю, показал способности, НО ЧЕ ТАК ЖЕСТКО ТО, АХАХА Ваще впервые эту хуйню услышал

😨3

1 Aug 2026, 12:08 UTC91 views8 reactionsread 10 August 2026
Photo

Честно говоря забыл даже, что сегодня праздник. Ну в целом поху, все равно ездил помогать другу с переездом, чухать чужого кота О, отправился

8

1 Aug 2026, 12:03 UTC85 viewsread 10 August 2026

Хотел отправить вам следом фотку чужого кота, но инет и впн решили отправить меня нахуй. Так что пока без фотки чужого кота

1 Aug 2026, 11:56 UTC85 viewsread 10 August 2026

Очень праздничная погодка для дня города сегодня конечно, ахах

27 Jul 2026, 14:08 UTC134 viewsread 10 August 2026

Сэкономил 2 года назад 5 тыщ, что бы сейчас платить 200. Вотэта успех

27 Jul 2026, 14:07 UTC128 viewsread 10 August 2026

Сходил к хирургам выслушать окончательный план лечения... Назначили по итогу мне 4 операции Четырехкратный ахуй словил я в этот момент, но хотя бы успокоили тем, что я не сдохну послезавтра (до этого мне говорили, что все пиздец торопитесь)

23 Jul 2026, 11:36 UTC155 views9 reactionsread 10 August 2026

Вот так даже сделаю Скорее всего пропущу все августовские мероприятия до полного выздоровления

💔9

23 Jul 2026, 11:33 UTC139 views4 reactionsread 10 August 2026

Не особо я представлял, что в июле буду бегать с операции на операцию

🕊4

28 Jun 2026, 19:57 UTC207 views11 reactionsread 10 August 2026
Photo

Кстати да, по Москве не опечатка. Из культурной столицы приехал в обычную. Щас тут немного чиллю и домой

👾7💋4

28 Jun 2026, 19:37 UTC181 views6 reactionsread 10 August 2026

Я ГРУЗИЛ ЭТО ПОЛТОРА!!! ГРЕБАННЫХ!!! ЧАСА!!! МОСКОВСКИЙ ИНТЕРНЕТ Я РОТ ЕБ Тут очень плохо ловит сеть, так что пришлось знатно так подождать, пока все загрузится ^^

💋4👾2

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

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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

“Хельхейм | рест” (@HelheimSteym), 123 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/HelheimSteym.

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.