Telegram RegisterThe public register of Telegram
Telegram profile photo for ЧВК РЕДАН

Channel

ЧВК РЕДАН

@chvkredan0

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

3,396subscribers

-30 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001597776817
TypeChannel
Username@chvkredan0
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/chvkredan0

Growth

3,3923,4263,4097 August 2026 — 3,426 subscribers7 August 2026 — 3,426 subscribers11 August 2026 — 3,413 subscribers14 August 2026 — 3,406 subscribers17 August 2026 — 3,404 subscribers20 August 2026 — 3,394 subscribers24 August 2026 — 3,392 subscribers27 August 2026 — 3,396 subscribers3,3967 August 202627 August 2026
8 measurements spanning 20 days, net -30. 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 3,387–3,431 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 01:083,396+4
24 Aug 2026, 11:343,392-2
20 Aug 2026, 17:233,394-10
17 Aug 2026, 21:333,404-2
14 Aug 2026, 22:333,406-7
11 Aug 2026, 08:233,413-13
7 Aug 2026, 09:013,426no change
7 Aug 2026, 08:553,426first reading

Engagement

20 posts held, back to 17 December 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof 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 20 posts for this entry, the most recent from 27 December 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

3,333 reactions across 20 posts, in 5 distinct kinds. The most used accounts for 37.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,24537.4%
😈99729.9%
🤡59817.9%
👍47714.3%
😱160.48%

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 20 of the 20 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 3,333reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 17 December 2024 to 27 December 2024, 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

27 Dec 2024, 18:01 UTC≈11,600 views336 reactionsread 7 August 2026
Photo

Пермь

231🤡59😈23👍21😱2

27 Dec 2024, 12:00 UTC≈10,900 views188 reactionsread 7 August 2026
Photo

Редан Отрадное @chvkredantut

131🤡26👍24😈7

27 Dec 2024, 06:01 UTC≈9,570 views221 reactionsread 7 August 2026
Photo

Хэпиньюэ Москва @chvkredantut

😈10667👍25🤡22😱1

26 Dec 2024, 18:00 UTC≈8,610 views150 reactionsread 7 August 2026
Photo

Смоленск👏 @chvkredantut

😈8535🤡18👍12

26 Dec 2024, 12:01 UTC≈7,030 views147 reactionsread 7 August 2026
Photo

Южное Бутово @chvkredantut

😈8030🤡22👍15

26 Dec 2024, 06:02 UTC≈6,240 views175 reactionsread 7 August 2026
Photo

Тюмень @chvkredantut

115😈25🤡21👍14

23 Dec 2024, 18:01 UTC≈6,050 views210 reactionsread 7 August 2026
Photo

редан из калика @chvkredantut

🤡109😈5629👍16

23 Dec 2024, 12:00 UTC≈5,610 views202 reactionsread 7 August 2026
Photo

Сап киев! @chvkredantut

😈124🤡3525👍16😱2

23 Dec 2024, 06:01 UTC≈4,970 views137 reactionsread 7 August 2026
Photo

На замке @chvkredantut

👍7628🤡17😈16

21 Dec 2024, 18:01 UTC≈4,690 views154 reactionsread 7 August 2026
Photo

Тамбовская область🍷 @chvkredantut

😈9428👍16🤡16

21 Dec 2024, 12:01 UTC≈4,390 views148 reactionsread 7 August 2026
Photo

сбп @chvkredantut

🤡8840👍12😈8

21 Dec 2024, 06:00 UTC≈4,200 views190 reactionsread 7 August 2026
Photo

Щовель из Подмосковья @chvkredantut

134😈21👍19🤡16

Showing the 12 most recent of 20 posts we hold for @chvkredan0. 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 — 403,213 of 1,624,174entries 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.

Mentions

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.

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.

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

“ЧВК РЕДАН” (@chvkredan0), 3,396 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/chvkredan0.

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.