Channel
@hey_dug
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
13subscribers
+1 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003154785222 |
|---|---|
| Type | Channel |
| Username | @hey_dug |
| Created | Between 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 1 October 2026 |
| On Telegram | t.me/hey_dug |
Other / unclassifiable — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 84% 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 |
|---|---|---|
| 1 Oct 2026, 15:37 | 13 | +1 |
| 12 Aug 2026, 06:15 | 12 | no change |
| 11 Aug 2026, 06:00 | 12 | first reading |
18 posts held, back to 19 May 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 18 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
28 reactions across 14 posts, in 9 distinct kinds. The most used accounts for 28.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😭 | 8 | 28.6% | |
| 🤯 | 5 | 17.9% | |
| custom 5319034516096951391 | 4 | 14.3% | |
| custom 5271537709721066822 | 3 | 10.7% | |
| 🔥 | 3 | 10.7% | |
| ❤ | 2 | 7.14% | |
| custom 5208915922609250347 | 1 | 3.57% | |
| 👀 | 1 | 3.57% | |
| 😁 | 1 | 3.57% |
Custom emoji. 3 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 14 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 28 reactions 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 19 May 2026 to 10 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.
> забронював в booking.com номер > гроші з карти не списало > подумав що все норм > пройшов день > відмінив бронювання > гроші списало через 20 хвилин > списало 2200 грн > а букінг коштує 2000 грн > я вахуї
😭2😁1
UPD: поки писав пост, то закинув другу спробу. Просто вирішив не робити повторне навчання на всіх даних.
custom 53190345160969513912
Спробував Titanic Competition в Kaggle, перший результат (залупа) Вирішив спробувати себе в ML (Machine Learning). Там є свій аналог Hello world - задача з Титаніком. Суть в тому, що потрібно передбачити, які пасажири виживуть. Чим точніше вгадав, тим більше молодець. Я наспарвді нічого за ML не шарю. Весь мій досвід, це рандомний хакатон, який був фул навайбкожений. Тому вирішив почати з найпростішого алгоритму - …
🤯2
Дакімакура для тарганів
👀1
Спробуйте задоксити мене
І не, я не спився. Просто відпочивав та чілив. Хоча, кому не похуй?
Якимось чудом пройшов в унік, хоча мені не хватало 250 балів 🤷♂️ Подався в іноземний ВНЗ та думав, що в мене з оцінками траблів не буде. А потім почалося: 1. НМТ їм нахуй не потрібен, тому похуй, що в мене там 200 з матана. Їм треба атестат. 2. В мене виходить 563, а треба 818 (да, обрав напрям з великим конкурсом). Починаю рахувати, в мене максимум може бути, ну... 700 (300 + 200 + 200). Шото тут не так 🤔 3. Зро…
🔥1
Купив нові навушники чек 🏋️ Попередні загубив а запасні поламались, коли я їх в рюкзак поклав. Продав чіловий мужик, який вже думав ціну підняти, поки я усі переваги навушників перераховував 😛 Можу продати за 2500 кста
🤯2❤1
Sticker, posted without a caption
БЛЯЯЯЯЯЯЯЯЯЯ, в мене дані загубились коли я процес прервав 👻 Виходить, в мене токени просто так згоріли
custom 53190345160969513911
Зараз запустив скрипт і під час виконання порахував, що воно сжере усі безкоштовні токени 😶 Причому я зупинити це не можу, тому просто мовча дивлюсь за своїм пройобом.
custom 52089159226092503471
Відбій повітряної тривоги, це в мене ВПН нахуй слав локальну мережу 🤷♂️
custom 52715377097210668221
Showing the 12 most recent of 18 posts we hold for @hey_dug. 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.
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.
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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“Hey Dug 🤨🕶🤏” (@hey_dug), 13 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/hey_dug.
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.