Telegram RegisterThe public register of Telegram

Channel

дватян

@dvatyan

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

1,316subscribers

-27 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003999577815
TypeChannel
Username@dvatyan
CreatedBetween 1 April 2026 and 27 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/dvatyan

Growth

1,3161,3431,329.57 August 2026 — 1,343 subscribers7 August 2026 — 1,341 subscribers10 August 2026 — 1,336 subscribers14 August 2026 — 1,316 subscribers7 August 202614 August 2026
4 measurements spanning 7 days, net -27. 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 1,312–1,347 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 14:041,316-20
10 Aug 2026, 22:591,336-5
7 Aug 2026, 22:521,341-2
7 Aug 2026, 03:011,343first reading

Engagement

20 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
60.3%
avg views ÷ 1,316 subscribers
Avg views / post
793
20 posts measured
Reaction rate
4.90%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 6 August 2026
Posts held20 (27 July 20266 August 2026)
Views total15,869
Reactions total777
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 03:01 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.

Reaction mix

777 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 26.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 542962398832415883120226.0%
custom 543150979249971239819925.6%
custom 534140738728887939013617.5%
custom 53551763867199321908210.6%
custom 53575587062947755437910.2%
custom 5407079412929667418648.24%
custom 5285474470574702366151.93%

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 areTelegram’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 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 777reactions 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 27 July 2026 to 6 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

6 Aug 2026, 16:22 UTC318 views23 reactionsread 7 August 2026

Такая прическа прикольная сегодня, но настроение ебнуть 2 часа кардио сильнее

custom 540707941292966741815custom 54296239883241588314custom 54315097924997123984

Signed двачан

6 Aug 2026, 16:13 UTC345 views30 reactionsread 7 August 2026

Извините, я помылся

custom 542962398832415883118custom 53414073872888793905custom 54070794129296674184custom 53551763867199321903

Signed двачан

6 Aug 2026, 16:13 UTC340 views23 reactionsread 7 August 2026
Video message

Video message, posted without a caption

custom 542962398832415883114custom 53575587062947755435custom 54315097924997123984

Signed двачан

5 Aug 2026, 17:04 UTC514 views20 reactionsread 7 August 2026

Че там за умник решил накрутку ебнуть

custom 540707941292966741820

Signed двачан

5 Aug 2026, 17:00 UTC519 views21 reactionsread 7 August 2026

🎉 Розыгрыш завершен! 🏆 Победители: 1. @supremeduwgs 2. @Vekorussxxf 3. @DOTRERAKL 4. @stxrvingmind 5. @Thelastofduck 6. @Lohagenko 🔍 Проверить результаты

custom 534140738728887939011custom 53575587062947755436custom 53551763867199321902custom 54315097924997123982

Signed Random Beast 🏆

5 Aug 2026, 13:01 UTC538 views55 reactionsread 7 August 2026
Photo

Чета приболел я, хуево ужас, сижу ем мороженое заедаю тоску

custom 543150979249971239830custom 534140738728887939014custom 54296239883241588317custom 53551763867199321904

Signed двачан

4 Aug 2026, 01:58 UTC639 views39 reactionsread 7 August 2026
Photo

Сегодня снова не сплю, походу теперь через день два спать буду. Чета 3 ночи думаю потренил 20 мин всего хотя днем думал отдых сделать денек и в итоге ебнул часик кардио в три ночи и думаю еще ебнуть часик и энергетик взять когда магаз откроется а то впадлу до круглосутки Ёбать

custom 534140738728887939030custom 52854744705747023665custom 54315097924997123984

Signed двачан

2 Aug 2026, 05:58 UTC895 views36 reactionsread 7 August 2026

По еблу видно, что двое суток не спал?

custom 534140738728887939019custom 535517638671993219010custom 54296239883241588314custom 54315097924997123983

Signed двачан

2 Aug 2026, 05:56 UTC873 views40 reactionsread 7 August 2026
Video

На зло помылся

custom 534140738728887939024custom 53551763867199321909custom 52854744705747023665custom 54315097924997123982

Signed двачан

1 Aug 2026, 17:53 UTC911 views61 reactionsread 7 August 2026
Photo

Второй день на энергетиках ток, даже уснуть не смог и до сих пор не хочу прикол

custom 535755870629477554330custom 542962398832415883112custom 53551763867199321908custom 53414073872888793906custom 54070794129296674183custom 52854744705747023661custom 54315097924997123981

Signed двачан

31 Jul 2026, 22:43 UTC≈1,020 views48 reactionsread 7 August 2026
Video

Возможно помоюсь

custom 542962398832415883129custom 543150979249971239813custom 53414073872888793906

Signed двачан

31 Jul 2026, 20:27 UTC≈1,080 views12 reactionsread 7 August 2026
Photo

⚡️РОЗЫГРЫШ⚡️ 🥇Милый сетик на выбор (1/2) 🥈Розовая акула 100см 🥉Кепка аутизм 😸Брелок и значки ⭐Тг премиум на 3 месяца ⭐️500 звезд Для участия быть активным подписчиком: @dvatyan @bloody_izuru @fembo и https://t.me/+7Evlk_D6s2pjYWEy ⏱Забираете подарком или деньгами, итоги 05.08.26 в 20:00 по мск

custom 53414073872888793906custom 53575587062947755434custom 54070794129296674182

Signed Random Beast 🏆

Showing the 12 most recent of 20 posts we hold for @dvatyan. 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 — 886,736 of 1,345,403entries 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 4 registered channels — 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“дватян” (@dvatyan), 1,316 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dvatyan.

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.