𝓹𝓱 𝓯𝓭. 𝓓𝓻.𝓢𝓽𝓸𝓷𝓮 𝒢𝑒𝓃
🔥10❤4🥰3

Channel
@hettso
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
172subscribers
+1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002101985966 |
|---|---|
| Type | Channel |
| Username | @hettso |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/hettso |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 10:34 | 172 | +1 |
| 9 Aug 2026, 02:21 | 171 | no change |
| 8 Aug 2026, 16:46 | 171 | first reading |
12 posts held, back to 2 April 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 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 12 posts for this entry, the most recent from 23 July 2026. An engagement rate over an empty window would be a number about nothing.
227 reactions across 12 posts, in 11 distinct kinds. The most used accounts for 26.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 60 | 26.4% | |
| ❤🔥 | 40 | 17.6% | |
| custom 5204244548674413984 | 28 | 12.3% | |
| custom 5449763553831558897 | 25 | 11.0% | |
| custom 5420219719342902228 | 23 | 10.1% | |
| 🔥 | 21 | 9.25% | |
| custom 5294391192048393015 | 19 | 8.37% | |
| 👍 | 5 | 2.20% | |
| 🥰 | 3 | 1.32% | |
| 🍌 | 2 | 0.881% | |
| 👎 | 1 | 0.441% |
Custom emoji. 4 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 12 of the 12 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 227 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 2 April 2026 to 23 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.
𝓹𝓱 𝓯𝓭. 𝓓𝓻.𝓢𝓽𝓸𝓷𝓮 𝒢𝑒𝓃
🔥10❤4🥰3
🖤🖤🖤 🖤🖤🖤 ph. fd. Подземелье вкусностей 🖤🖤 🖤🖤 🖤🖤
custom 520424454867441398416custom 52943911920483930158custom 54497635538315588978❤4custom 54202197193429022281
🔵🌸🟣🍃🌼🍃🟣🌸🔵🐱
custom 542021971934290222810❤🔥6
Бу (это я на моконе типо хз не шарю)
❤16custom 52943911920483930154❤🔥3👍1
Ждите имбу
❤🔥6🍌2
Ну вот как-то так
custom 542021971934290222810❤4👍4
i believe in toki wartooth supremacy #DETHKLOK мфейс нейтан токи ((всё кликабельно)) сквиз — ???.? photograph ⚠️‼️‼️МАКСИМАЛЬНЫЙ РТ ПЖЛ Я ПЫТАЮСЬ ВЕРНУТЬСЯ В КОСП КМ;(((
❤3❤🔥2🔥2👎1custom 54497635538315588971
Никто не угадал, всем по 0 сундучков
❤14❤🔥7🔥4
Челендж угадайте на кого косплей (нет, это не крис)
❤🔥4❤3custom 54202197193429022282
Всем доброго дня Хотела сказать, что у меня появился мини маназинчик, где собираюсь выставлять разные украшения на продажу. Ну и постараюсь со временем выкладывать туда побольше контента: процессы, новые товары и все в этом духе Кому интересно, переходите по ссылке https://t.me/hets_shop
❤🔥8❤5custom 54497635538315588973🔥1
強くなるため 忘れた笑顔 きっと二人なら 取り戻す Shin. ph. fd. Nana
custom 52042445486744139847custom 52943911920483930156🔥4❤🔥3custom 54497635538315588971
ᏇᏂᏗ𐐆'Ꮥ ᏇᏒᎧᏁᎶ Ꮗ𐌉𐐆Ꮒ ᎩᎧᏬ, ᏕᎧ ᏕᏬᎴᎴᏋᏁᏝᎩ? ᏂᏋ'Ꮥ 𐐆ᏂᏋ ᏰᏋᏕ𐐆 ᎴᏗᎴ 𐌉Ꮑ 𐐆ᏂᏋ ᏇᎧᏒᏝᎴ! ᏂᏋ 𐐆ᏗᏬᎶᏂ𐐆 ᙏᏋ ᏕᎧ ᙏᏬ૮Ꮒ. fd - made in abyss ph
custom 544976355383155889712❤7custom 52042445486744139845❤🔥1custom 52943911920483930151
Showing the 12 most recent of 12 posts we hold for @hettso. 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.
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.
Named by 4 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@hettso named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“Hetso durak” (@hettso), 172 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/hettso.
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.