Channel
@VRD_LIFE
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
206subscribers
+11 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003609218950 |
|---|---|
| Type | Channel |
| Username | @VRD_LIFE |
| Created | Between 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/VRD_LIFE |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 09:52 | 206 | +11 |
| 8 Aug 2026, 11:47 | 195 | no change |
| 8 Aug 2026, 07:15 | 195 | first reading |
20 posts held, back to 5 August 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 pageof Telegram’s post history, 20 posts per page.
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. It is computed over the 13 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (5 August 2026 – 8 August 2026) |
| Views total | 1,825 |
| Reactions total | 89 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 11:47 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.
Measured directly from 3 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.
89 reactions across 13 posts, in 10 distinct kinds. The most used accounts for 15.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5193176237563997320 | 14 | 15.7% | |
| custom 5314468171292383432 | 14 | 15.7% | |
| custom 5253710305497742895 | 12 | 13.5% | |
| custom 5458367094879969458 | 11 | 12.4% | |
| custom 5458891214034069178 | 9 | 10.1% | |
| custom 5285040459834488790 | 8 | 8.99% | |
| custom 5192754205487559409 | 6 | 6.74% | |
| custom 5317026511511915236 | 6 | 6.74% | |
| custom 5463039890449003865 | 5 | 5.62% | |
| custom 5280670034258073455 | 4 | 4.49% |
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 13 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 89reactions 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 5 August 2026 to 8 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.
🔤🔤🔤🔤🔤🔳🔤🔤🔤🔤🔤 🍰🍰🍰🍰🍰🍰🍰🍰🍰🍰🍰 ✨ Видео от Макимы ✨Идея: не наша ✨Тик ток: overdose_fl00d ✨Ссылка на видео: скоро будет… #VRD_видео 💤Просим продвигать наши видео,спасибо!
custom 53170265115119152364custom 52537103054977428952custom 53144681712923834322custom 52806700342580734551custom 54583670948799694581
Signed 𝗦𝗮𝘁𝗼𝘀𝗵𝗶 #𝑬𝑺𝑫⁸¹²
Удачи
Signed 𝗥𝗶𝘇𝗲𝘄𝗶 #𝗺𝘀𝗵
Sticker, posted without a caption
custom 52537103054977428952custom 52850404598344887901custom 54583670948799694581custom 54588912140340691781
Signed 𝗦𝗮𝘁𝗼𝘀𝗵𝗶 #𝑬𝑺𝑫⁸¹²
Ладно все заебали анон тайм еще завтра будет
custom 51927542054875594094custom 51931762375639973202custom 52537103054977428951
Signed 𝗦𝗮𝘁𝗼𝘀𝗵𝗶 #𝑬𝑺𝑫⁸¹²
Разрыв с - @KP_infoo Причина: моя инициатива
Signed 𝗥𝗶𝘇𝗲𝘄𝗶 #𝗺𝘀𝗵
#VRD_репост
Signed 𝗥𝗶𝘇𝗲𝘄𝗶 #𝗺𝘀𝗵
#VRD_репост
custom 52537103054977428951custom 52850404598344887901custom 54588912140340691781
Signed 𝗥𝗶𝘇𝗲𝘄𝗶 #𝗺𝘀𝗵
#VRD_репост
custom 51931762375639973201custom 54583670948799694581custom 54588912140340691781
Signed 𝗥𝗶𝘇𝗲𝘄𝗶 #𝗺𝘀𝗵
🔤🔤🔤🔤🔤🔳🔤🔤🔤🔤🔤 🍰🍰🍰🍰🍰🍰🍰🍰🍰🍰🍰 ✨ Видео от С.С ✨Идея: хз ✨Тик ток: overdose_fl00d ✨Ссылка на видео: скоро будет… #VRD_видео 💤Просим продвигать наши видео,спасибо!
custom 52850404598344887904custom 51931762375639973202custom 52537103054977428952custom 53144681712923834321custom 54583670948799694581
Signed 𝗦𝗮𝘁𝗼𝘀𝗵𝗶 #𝑬𝑺𝑫⁸¹²
Sticker, posted without a caption
Signed 𝗥𝗶𝘇𝗲𝘄𝗶 #𝗺𝘀𝗵
ׅ 𝆬 ᩧ۶ 𝙉𝙀𝙒 𝙐𝙉𝙄𝙊𝙉 ৎ ᩧ ׅ 𝆬⠀ ─────────── « 𓂃⩇⩇.⩇⩇/𝒁𝖊r𝔬-𝑫a𝖞 𝑳𝖊g𝒂𝖈𝒚𓏴 ۫ ۫ 𝅄ׄ » 𝙄𝙉𝙁𝙊: @InfoZer0Day 𝙇𝙄𝙁𝙀: @LifeZeroDays 𝙏𝙍𝘼𝘾𝙆𝙀𝙍: @ViVi_0013 « 𝙊𝙑𝙀𝙍𝘿𝙊𝙎𝙀 » 𝙄𝙉𝙁𝙊: @INFO_VRD 𝙇𝙄𝙁𝙀: @VRD_life 𝙏𝙍𝘼𝘾𝙆𝙀𝙍: @rlzewi 𝟎𝟕.𝟎𝟖.𝟐𝟔 Ꮋᴀдᴇюᴄь нᴀ дᴏᴧᴦᴏᴇ и ᴋᴩᴇᴨᴋᴏᴇ ᴄᴏᴛᴩудничᴇᴄᴛʙᴏ. #VRD_союз
custom 53144681712923834321custom 54588912140340691781custom 54630398904490038651
Signed 𝗥𝗶𝘇𝗲𝘄𝗶 #𝗺𝘀𝗵
сатоши я ревную тебя к овердозу, выцди пожалуцста....
custom 51931762375639973204custom 51927542054875594092custom 53144681712923834322custom 53170265115119152362custom 54583670948799694582custom 52806700342580734551custom 52850404598344887901custom 54588912140340691781
Signed 𝗦𝗮𝘁𝗼𝘀𝗵𝗶 #𝑬𝑺𝑫⁸¹²
Showing the 12 most recent of 20 posts we hold for @VRD_LIFE. 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 — 26,051 of 1,548,671entries 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.
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.
Named by 12 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.
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.
@VRD_LIFE named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“𝙊𝙑𝙀𝙍𝘿𝙊𝙎𝙀 || Лᴀйɸ ᴋᴀнᴀᴧ” (@VRD_LIFE), 206 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/VRD_LIFE.
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.