я перехожу на свой старый канал если кому то надо вот ссылка 👉 https://t.me/dycheshhh
Signed 𝗝𝗼𝗸𝗲𝗿.

Channel
@dychesh
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
89subscribers
+66 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003565794055 |
|---|---|
| Type | Channel |
| Username | @dychesh |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/dychesh |
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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 |
|---|---|---|
| 6 Oct 2026, 13:40 | 89 | -2 |
| 26 Sept 2026, 12:59 | 91 | -2 |
| 14 Sept 2026, 03:01 | 93 | +1 |
| 29 Aug 2026, 06:49 | 92 | -2 |
| 22 Aug 2026, 00:23 | 94 | +71 |
| 11 Aug 2026, 11:32 | 23 | no change |
| 7 Aug 2026, 19:24 | 23 | first reading |
17 posts held, back to 16 June 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 17 posts for this entry, the most recent from 12 July 2026. An engagement rate over an empty window would be a number about nothing.
19 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 47.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5150273761999587533 | 9 | 47.4% | |
| custom 5368627992362774892 | 7 | 36.8% | |
| custom 5368576293841433373 | 3 | 15.8% |
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 4 of the 17 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 16 June 2026 to 12 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.
я перехожу на свой старый канал если кому то надо вот ссылка 👉 https://t.me/dycheshhh
Signed 𝗝𝗼𝗸𝗲𝗿.
SH3 W黄4nt,😽"th4t 🤩 L0v3y- d0v3y Th4T . . KīsS, k1Ss💋 1n M1ñD ✨S3e F4N7eß1zE🥰 施 'B0ú7 Gë7tIn'🔵W1#T Mē💀
Signed 𝗦𝗻𝗼𝗼𝗽 𝗱𝗼𝗴𝗴𝘆.
https://t.me/dycheshhh
Signed 𝗦𝗻𝗼𝗼𝗽 𝗱𝗼𝗴𝗴𝘆.
любая песня эминема мне кажется тебя опишет
custom 51502737619995875333
Signed 𝗦𝗻𝗼𝗼𝗽 𝗱𝗼𝗴𝗴𝘆.
Sticker, posted without a caption
Signed 𝗦𝗻𝗼𝗼𝗽 𝗱𝗼𝗴𝗴𝘆.
😀😀😀😀😀😀😀😀
Signed 𝗦𝗻𝗼𝗼𝗽 𝗱𝗼𝗴𝗴𝘆.
Sticker, posted without a caption
Signed 𝗦𝗻𝗼𝗼𝗽 𝗱𝗼𝗴𝗴𝘆.
ЕБАТЬ ПРОФАК АХУЕННЫЙ
Signed 𝗦𝗻𝗼𝗼𝗽 𝗱𝗼𝗴𝗴𝘆.
👅👅👅
custom 51502737619995875331custom 53686279923627748921
Signed 𝗦𝗻𝗼𝗼𝗽 𝗱𝗼𝗴𝗴𝘆.
Sticker, posted without a caption
Signed 𝟱𝟬𝗖𝗘𝗡𝗧.
— я принесу тебе лето, даже если весь мир останется в ноябре
custom 53686279923627748923custom 51502737619995875332
Signed 𝟱𝟬𝗖𝗘𝗡𝗧.
Sticker, posted without a caption
Signed motherfucker.ʳⁿ
Showing the 12 most recent of 17 posts we hold for @dychesh. 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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“Motherfucker.” (@dychesh), 89 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/dychesh.
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.