Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝑉𝑎𝑑𝑖𝑚_𝐷𝑟𝑢𝑚𝑚𝑒𝑟

Channel

𝑉𝑎𝑑𝑖𝑚_𝐷𝑟𝑢𝑚𝑚𝑒𝑟

@vadrum2000

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

145subscribers

+1 since we began measuring on 31 August 2026

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

Register entry

Telegram ID-1001794928300
TypeChannel
Username@vadrum2000
CreatedBetween 1 January 2022 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live18 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/vadrum2000

Topic

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 25 September 2026 and assigned it the closest of 31 fixed categories, at 45% 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.

Growth

144145144.531 August 2026 — 144 subscribers31 August 2026 — 144 subscribers18 September 2026 — 145 subscribers31 August 202618 September 2026
3 measurements spanning 19 days, net +1. 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 144–145 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 15:59145+1
31 Aug 2026, 20:15144no change
31 Aug 2026, 03:34144first reading

Engagement

17 posts held, back to 26 July 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.

ERR · 30 days
35.2%
avg views ÷ 145 subscribers
Avg views / post
51.0
3 posts measured
Reaction rate
14.4%
reactions ÷ views · ER floor
Posts in window
3
of 17 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 August 2026
Posts held17 (26 July 2026 – 30 August 2026)
Views total153
Reactions total22
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken31 Aug 2026, 03:34 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
5m 27s
Average length
30s

Measured directly from 11 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

117 reactions across 17 posts, in 12 distinct kinds. The most used accounts for 47.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤5547.0%
🔥2723.1%
😍86.84%
👍54.27%
💯43.42%
😁43.42%
🤣43.42%
😢32.56%
🍓21.71%
👨‍💻21.71%
🥴21.71%
💅10.855%

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 17 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 117 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 26 July 2026 to 30 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.

Recent posts

30 Aug 2026, 05:40 UTC33 views6 reactionsread 31 August 2026
Photo

Вопросов надеюсь больше не осталось🤣🤣🤣

🤣4❤1👨‍💻1

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

29 Aug 2026, 19:04 UTC39 views7 reactionsread 31 August 2026
Video

первый мой турнир по бадминтону 🙌🏽🔥

🔥3❤2💅1😍1

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

28 Aug 2026, 20:05 UTC81 views9 reactionsread 31 August 2026
Video

Новое новое! Но не судим строго!!

❤6😍2🔥1

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

25 Aug 2026, 19:25 UTC85 views6 reactionsread 31 August 2026
Video

Важно!

🔥3❤2💯1

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

22 Aug 2026, 17:37 UTC109 views10 reactionsread 31 August 2026
Photo

У вас бывало такое, что вы работаете, работаете, работаете, а когда вдруг выбираетесь просто посмотреть кино — чувствуете угнетение внутри? Будто отдыхать в конце недели — это что-то нелегальное 😅

😢3❤2😁2👍1👨‍💻1💯1

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

18 Aug 2026, 14:47 UTC127 views1 reactionsread 31 August 2026
Poll

Напрягает, когда консультанты атакуют прямо с порога?

  1. Да,сразу пропадает желание что-то покупать29%
  2. Скорее да, люблю выбирать молча и спокойно76%
  3. Нет,отношусь спокойно это их работа14%
  4. Наоборот, экономит мне время0%

The shares total 119%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

❤1

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

16 Aug 2026, 15:15 UTC114 views6 reactionsread 31 August 2026
Video

Что если вспомнить Советские Песни))

❤4🔥2

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

14 Aug 2026, 18:11 UTC119 views5 reactionsread 31 August 2026
Video

🔉А что это знааачит?😂

❤4😁1

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

13 Aug 2026, 13:57 UTC117 views5 reactionsread 31 August 2026
Video

🦁

❤3🔥2

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

8 Aug 2026, 16:45 UTC143 views7 reactionsread 31 August 2026
Video

Пока только так 🫡 Позже могу закинуть Какие конкретно делаю упражнения 🙌🏽🫠

🔥3❤2👍1😁1

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

5 Aug 2026, 19:23 UTC157 views5 reactionsread 31 August 2026

Если я не сяду на поперечный шпагат до 5.09.2026 (ровно через месяц) то разыграю 3000 рублей среди тех, кто в комментах напишет "Не сядешь"».🫢😄🫡

❤5

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

3 Aug 2026, 17:22 UTC170 views7 reactionsread 31 August 2026
Video

Нравится эта песня уж очень давно. Не мог не снять видос 🤷‍♂️

❤4🍓2👍1

Signed 𝐕𝐚𝐝𝐢𝐦 𝐊𝐨𝐯𝐚𝐥𝐞𝐯

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

18 Aug 2026, 14:47 UTCAnonymous Poll21 voters

Напрягает, когда консультанты атакуют прямо с порога?

  1. Да,сразу пропадает желание что-то покупать29%
  2. Скорее да, люблю выбирать молча и спокойно76%
  3. Нет,отношусь спокойно это их работа14%
  4. Наоборот, экономит мне время0%

The shares total 119%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 17 most recent posts we hold, published 26 July 2026 to 30 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“𝑉𝑎𝑑𝑖𝑚_𝐷𝑟𝑢𝑚𝑚𝑒𝑟” (@vadrum2000), 145 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/vadrum2000.

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.