Channel
@deniskujdin
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
84subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001577406323 |
|---|---|
| Type | Channel |
| Username | @deniskujdin |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 5 times, most recently 9 October 2026 |
| On Telegram | t.me/deniskujdin |
Personal blog — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 |
|---|---|---|
| 28 Aug 2026, 12:23 | 84 | +1 |
| 14 Aug 2026, 05:08 | 83 | -1 |
| 9 Aug 2026, 17:16 | 84 | no change |
| 7 Aug 2026, 08:56 | 84 | first reading |
10 posts held, back to 13 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 10 posts for this entry, the most recent from 20 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
170 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 23.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5255979839231379022 | 40 | 23.5% | |
| custom 5348343042212381365 | 30 | 17.6% | |
| custom 5222292529533167322 | 29 | 17.1% | |
| custom 5208895366895792681 | 22 | 12.9% | |
| custom 5429493966779224299 | 19 | 11.2% | |
| custom 5355014749920709843 | 15 | 8.82% | |
| custom 5242677827299450340 | 10 | 5.88% | |
| custom 5301274628759506668 | 5 | 2.94% |
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 10 of the 10 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 170 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 13 May 2026 to 20 June 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.
тот самый день Ди уехала 77/ХХХ
custom 52222925295331673227custom 53483430422123813654custom 54294939667792242994custom 53012746287595066682custom 52088953668957926811custom 53550147499207098431
дом милый дом сменил дислокацию на эту весну. Но уже соскучился 76/ХХХ
custom 52559798392313790225custom 52222925295331673224custom 52088953668957926813custom 54294939667792242992custom 52426778272994503401custom 53483430422123813651custom 53550147499207098431
впихнуть невпихуемое эт я по работе ездил, мысли? 75/ХХХ
custom 54294939667792242997custom 52426778272994503404custom 53550147499207098434custom 52222925295331673221
горячий грушевый пирог если вы уважаете меня, обязательно попробуйте в Mosca это произведение искусства. Мы уже какой раз там бываем и до сих пор это что-то гастрономическое! 74/ХХХ
custom 53483430422123813656custom 52559798392313790225custom 53012746287595066683custom 52222925295331673222custom 52088953668957926811custom 52426778272994503401custom 53550147499207098431custom 54294939667792242991
🪫…🔋 просто хорошо проводим время 73/ХХХ
custom 53483430422123813655custom 52559798392313790224custom 52088953668957926813custom 52222925295331673221custom 52426778272994503401custom 53550147499207098431custom 54294939667792242991
я стал дядей теперь в планах быть тем самым, кто привозит крутые подарки по праздникам 😁 72/ХХХ
custom 52559798392313790229custom 52222925295331673224custom 53483430422123813653custom 53550147499207098432custom 52088953668957926811custom 54294939667792242991
смак умеем красиво кушать. Приглашайте 71/ХХХ
custom 52088953668957926814custom 52559798392313790224custom 53483430422123813654custom 52222925295331673223custom 53550147499207098431custom 54294939667792242991
волшебство второй раз уже хожу на зимнее представление в национальный центр. И получается с детских сказок на маминой работе не уходил 🤭 70/ХХХ
custom 52088953668957926815custom 52559798392313790224custom 52222925295331673223custom 52426778272994503401custom 53483430422123813651custom 53550147499207098431custom 54294939667792242991
Амадей очень круто! Моцарт действительно «рок звезда» своего времени 🤭 69/ХХХ
custom 52559798392313790225custom 52222925295331673223custom 53550147499207098433custom 52088953668957926811custom 52426778272994503401custom 53483430422123813651custom 54294939667792242991
зима в сердце в этом году была одна из самых запоминающихся зим по количеству снегопадов 68/ХХХ
custom 53483430422123813655custom 52559798392313790224custom 52088953668957926813custom 52222925295331673221custom 52426778272994503401
Showing the 10 most recent of 10 posts we hold for @deniskujdin. 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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“ДЕНИСУС НА СВЯЗИ” (@deniskujdin), 84 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/deniskujdin.
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.