Channel
@hellwooddct
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Declared links · Cite this entry
259subscribers
-2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002116842992 |
|---|---|
| Type | Channel |
| Username | @hellwooddct |
| 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 | 17 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/hellwooddct |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 62% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 13:01 | 259 | -2 |
| 24 Aug 2026, 18:13 | 261 | -2 |
| 17 Aug 2026, 13:17 | 263 | +2 |
| 8 Aug 2026, 09:04 | 261 | no change |
| 8 Aug 2026, 05:30 | 261 | first reading |
7 posts held, back to 27 July 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 7 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
186 reactions across 7 posts, in 10 distinct kinds. The most used accounts for 19.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5445071349305334117 | 37 | 19.9% | |
| custom 5463369911441055516 | 31 | 16.7% | |
| custom 5462928676565834593 | 30 | 16.1% | |
| custom 5463176272840515040 | 26 | 14.0% | |
| custom 5453919952597701544 | 18 | 9.68% | |
| custom 5442825197373639735 | 11 | 5.91% | |
| custom 5463228186110223262 | 11 | 5.91% | |
| custom 5256119683366542085 | 10 | 5.38% | |
| custom 5454070950762927823 | 7 | 3.76% | |
| custom 5217811938045629684 | 5 | 2.69% |
Custom emoji. Every row above is a 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 7 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 186 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 27 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.
⛓️💥slay, snack, wait [xlov - hips] #krddc
custom 546336991144105551613custom 544507134930533411710custom 54632281861102232626custom 54629286765658345934custom 54428251973736397352custom 54539199525977015442
⠀⠀⠀⠀⠀⠀⠀⠀「 #hwfest 」 ⠀⠀🗡️ 20260719 косплей день ⠀⠀⠀⠀plave – dash ph; https://vk.ru/id657304359
custom 54539199525977015448custom 54450713493053341177custom 54629286765658345933custom 54633699114410555162
⠀⠀⠀⠀⠀⠀⠀⠀「 #hwfest 」 ⠀⠀🗡️ 20260719 косплей день ⠀⠀⠀⠀plave – dash ph; https://vk.com/id789810657
custom 54631762728405150409custom 54633699114410555169custom 54450713493053341178custom 54629286765658345931
⠀⠀⠀⠀⠀⠀⠀⠀「 #hwfest 」 ⠀⠀🗡️ 20260719 косплей день ⠀⠀⠀⠀plave – dash ph; https://vk.com/id789810657
custom 54631762728405150406custom 54428251973736397354custom 52178119380456296843custom 52561196833665420852
⠀⠀⠀⠀⠀⠀⠀⠀「 #hwfest 」 ⠀⠀🗡️ 20260719 косплей день ⠀⠀⠀⠀plave – dash ph; https://t.me/foggghuman
custom 54450713493053341178custom 54629286765658345937custom 54539199525977015446custom 54632281861102232624
⠀⠀⠀⠀⠀⠀⠀⠀「 #hwfest 」 ⠀⠀🖤 20260719 flow fest ⠀⠀⠀⠀enhypen – knife ⠀⠀⠀⠀history – what am i to you ph; https://t.me/whoisktotec
custom 546292867656583459314custom 54540709507629278237custom 54428251973736397355custom 52178119380456296842custom 54450713493053341172custom 54633699114410555162custom 54539199525977015441
⠀⠀⠀⠀⠀⠀⠀⠀「 #hwfest 」 ⠀⠀🗡️ 20260719 flow fest ⠀⠀⠀⠀enhypen – knife ph; https://t.me/whoisktotec
custom 546317627284051504011custom 52561196833665420858custom 54633699114410555165custom 54450713493053341172custom 54539199525977015441custom 54629286765658345931custom 54632281861102232621
Showing the 7 most recent of 7 posts we hold for @hellwooddct. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 3 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.
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“𝐇𝐄𝐋𝐋𝐖𝐎𝐎𝐃 †” (@hellwooddct), 259 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/hellwooddct.
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.