Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝑫

Channel

𝑫

@kdrvvs

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

44subscribers

-4 since we began measuring on 27 August 2026

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

Register entry

Telegram ID-1002083014034
TypeChannel
Username@kdrvvs
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 August 2026
Last confirmed live25 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/kdrvvs

Growth

44484627 August 2026 — 48 subscribers27 August 2026 — 48 subscribers4 September 2026 — 46 subscribers25 September 2026 — 44 subscribers27 August 202625 September 2026
4 measurements spanning 29 days, net -4. 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 43–49 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 18:1444-2
4 Sept 2026, 18:1446-2
27 Aug 2026, 11:3048no change
27 Aug 2026, 11:1648first reading

Engagement

20 posts held, back to 30 March 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 20 posts for this entry, the most recent from 13 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
47s
Average length
12s

Measured directly from 4 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.

Reaction mix

207 reactions across 18 posts, in 14 distinct kinds. The most used accounts for 18.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54291729738084082253918.8%
custom 53685916569394415552914.0%
custom 53144893884308052742713.0%
custom 5415778173403033517178.21%
custom 5379725388991713802167.73%
custom 5454213320338861493167.73%
custom 5463095673484236737167.73%
custom 5242472609467085687104.83%
custom 525581904424575252294.35%
custom 525594934496357635073.38%
custom 527604811257665088873.38%
custom 525398663080865181762.90%
custom 523322665727533425752.42%
custom 519720736072404025131.45%

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 18 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 207 reactions 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 30 March 2026 to 13 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.

Telegram Stars

Stars received
28
across the posts below
Posts paid on
16
of 18 we hold a reading for · 89%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kdrvvs. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 30 March 2026 to 13 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

13 Aug 2026, 20:54 UTC62 views13 reactionsread 27 August 2026
Photo

Photo, posted without a caption

custom 52424726094670856875custom 54291729738084082254custom 52332266572753342573custom 54542133203388614931

26 Jul 2026, 19:13 UTC131 views7 reactions1 Starread 27 August 2026
Video

Video, posted without a caption

custom 51972073607240402513custom 52332266572753342572custom 52424726094670856871custom 54542133203388614931

19 Jul 2026, 19:01 UTC125 views10 reactions1 Starread 27 August 2026

Posted without readable text

custom 54291729738084082255custom 53685916569394415553custom 54157781734030335172

17 Jul 2026, 21:05 UTC117 views15 reactions3 Starsread 27 August 2026
Photo

🐈

custom 52760481125766508887custom 53685916569394415555custom 52424726094670856873

14 Jul 2026, 11:19 UTC115 views12 reactions2 Starsread 27 August 2026
File

1:18

custom 54542133203388614937custom 54157781734030335172custom 53685916569394415551custom 54291729738084082251custom 54630956734842367371

4 Jul 2026, 18:30 UTC158 views11 reactions1 Starread 27 August 2026
Video

Video, posted without a caption

custom 54542133203388614935custom 54157781734030335173custom 53685916569394415552custom 53144893884308052741

4 Jul 2026, 16:35 UTC130 views13 reactions3 Starsread 27 August 2026
Photo

Работяги🤟🏿

custom 53685916569394415556custom 54291729738084082253custom 54542133203388614932custom 53144893884308052741custom 54157781734030335171

1 Jul 2026, 14:01 UTC127 views8 reactions1 Starread 27 August 2026
Photo

💆🏻‍♂️

custom 53685916569394415554custom 54291729738084082254

24 Jun 2026, 13:18 UTC156 views12 reactions2 Starsread 27 August 2026
Photo

🧽

custom 53685916569394415554custom 54157781734030335174custom 54291729738084082254

20 Jun 2026, 17:39 UTC160 views12 reactions5 Starsread 27 August 2026
Photo

Photo, posted without a caption

custom 53685916569394415554custom 54157781734030335172custom 54630956734842367372custom 52424726094670856871custom 52539866308086518171custom 52558190442457525221custom 52559493449635763501

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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.

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

“𝑫” (@kdrvvs), 44 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/kdrvvs.

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.