Telegram RegisterThe public register of Telegram
Telegram profile photo for 「HUSKERDUST CONF’」

Channel

「HUSKERDUST CONF’」

@dustyhusk

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

574subscribers

+7 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003478456005
TypeChannel
Username@dustyhusk
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/dustyhusk

Growth

567574570.58 August 2026 — 567 subscribers8 August 2026 — 567 subscribers16 August 2026 — 574 subscribers8 August 202616 August 2026
3 measurements spanning 8 days, net +7. 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 566–575 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 05:57574+7
8 Aug 2026, 03:32567no change
8 Aug 2026, 00:20567first reading

Engagement

18 posts held, back to 25 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
32.0%
avg views ÷ 574 subscribers
Avg views / post
184
17 posts measured
Reaction rate
18.6%
reactions ÷ views · ER floor
Posts in window
18
of 18 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 July 2026
Posts held18 (25 July 202626 July 2026)
Views total3,121
Reactions total579
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:32 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

579 reactions across 17 posts, in 12 distinct kinds. The most used accounts for 39.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
22939.6%
custom 534831334251354874611519.9%
💔7813.5%
custom 5451820113021920857447.60%
custom 5348321245253374622295.01%
💘284.84%
💋213.63%
custom 5325852428787006841142.42%
custom 544273872679707570191.55%
custom 544515906112745560371.21%
custom 532816536316518417930.518%
😢20.345%

Custom emoji. 7 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 areTelegram’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 17 of the 18 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 579reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

Recent posts

26 Jul 2026, 19:46 UTCviews —

「HUSKERDUST CONF’」 pinned «❗️Канал уходит в 🔤🔤🔤🔤 до 9 августа»

26 Jul 2026, 19:46 UTC226 views63 reactionsread 8 August 2026

❗️Канал уходит в 🔤🔤🔤🔤 до 9 августа

💔48custom 5325852428787006841123

26 Jul 2026, 19:03 UTC232 views40 reactionsread 8 August 2026
Photo

「HUSKERDUST CONF’」 🌿🐱🐱🐱🐱🐱🌿 cr: @ vanillabrwnsugr ∥ 💬 ∥ ❣️ флуд ∥ буст ∥ предложка tags: #duskyconf • #huskerdust • #husk • #angeldust • #art • #tranclate

26custom 54518201130219208576💘5custom 53483133425135487462custom 54427387267970757011

26 Jul 2026, 18:04 UTC227 views32 reactionsread 8 August 2026
Photo

「HUSKERDUST CONF’」 🌿🐱🐱🐱🐱🐱🌿 cr: @ madelezabeth ∥ 💬 ∥ ❣️ флуд ∥ буст ∥ предложка tags: #duskyconf • #huskerdust • #husk • #angeldust • #art

custom 534831334251354874619custom 54427387267970757016custom 545182011302192085752

26 Jul 2026, 17:05 UTC201 views28 reactionsread 8 August 2026
Photo

「HUSKERDUST CONF’」 🌿🐱🐱🐱🐱🐱🌿 cr: @ oil_abr ∥ 💬 ∥ ❣️ флуд ∥ буст ∥ предложка tags: #duskyconf • #huskerdust • #husk • #angeldust • #art

16custom 53483133425135487466custom 54451590611274556036

26 Jul 2026, 16:02 UTC193 views36 reactionsread 8 August 2026
Photo

「HUSKERDUST CONF’」 🌿🐱🐱🐱🐱🐱🌿 cr: @ red-tea-antis ∥ 💬 ∥ ❣️ флуд ∥ буст ∥ предложка tags: #duskyconf • #huskerdust • #husk • #angeldust • #art

21custom 53483133425135487468custom 53483212452533746227

26 Jul 2026, 15:01 UTC171 views37 reactionsread 8 August 2026
Photo

「HUSKERDUST CONF’」 🌿🐱🐱🐱🐱🐱🌿 cr: @ cozycasbee ∥ 💬 ∥ ❣️ флуд ∥ буст ∥ предложка tags: #duskyconf • #huskerdust • #husk • #angeldust • #art

23custom 53483212452533746226custom 53483133425135487464💔3custom 53258524287870068411

26 Jul 2026, 14:01 UTC167 views34 reactionsread 8 August 2026
Photo

「HUSKERDUST CONF’」 🌿🐱🐱🐱🐱🐱🌿 cr: @ halun_030 ∥ 💬 ∥ ❣️ флуд ∥ буст ∥ предложка tags: #duskyconf • #huskerdust • #husk • #angeldust • #art

20💋7💘7

26 Jul 2026, 13:02 UTC173 views27 reactionsread 8 August 2026
Photo

「HUSKERDUST CONF’」 🌿🐱🐱🐱🐱🐱🌿 cr: @ Azimech_7 ∥ 💬 ∥ ❣️ флуд ∥ буст ∥ предложка tags: #duskyconf • #huskerdust • #husk • #angeldust • #art

💋14custom 534831334251354874664custom 53483212452533746223

26 Jul 2026, 12:02 UTC166 views24 reactionsread 8 August 2026
Photo

「HUSKERDUST CONF’」 🌿🐱🐱🐱🐱🐱🌿 cr: @ enaiC31hzbn ∥ 💬 ∥ ❣️ флуд ∥ буст ∥ предложка tags: #duskyconf • #angeldust • #art

12💘5custom 54518201130219208575custom 54427387267970757012

26 Jul 2026, 11:04 UTC161 views28 reactionsread 8 August 2026
Photo

「HUSKERDUST CONF’」 🌿🐱🐱🐱🐱🐱🌿 cr: @ pilepile000 ∥ 💬 ∥ ❣️ флуд ∥ буст ∥ предложка tags: #duskyconf • #husk • #art

16custom 53483133425135487466custom 54518201130219208576

26 Jul 2026, 10:01 UTC164 views30 reactionsread 8 August 2026
Photo

「HUSKERDUST CONF’」 🌿🐱🐱🐱🐱🐱🌿 TAKE FR ANON ❣️ ❣️ флуд ∥ буст ∥ предложка мяу 🍓🍓 тгк :: @meow_meow3337 tags: #duskyconf • #take

custom 534831334251354874617custom 53483212452533746226custom 54518201130219208576💘1

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

Citation-graph rank

Citation-graph rank — 758,453 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

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.

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

“「HUSKERDUST CONF’」” (@dustyhusk), 574 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/dustyhusk.

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.