Telegram RegisterThe public register of Telegram
Telegram profile photo for vsl

Channel

vsl

@vas1lievich

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

119subscribers

-7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003511760728
TypeChannel
Username@vas1lievich
Created27 January 2026measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live31 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/vas1lievich

Growth

1191271237 August 2026 — 126 subscribers8 August 2026 — 127 subscribers9 August 2026 — 127 subscribers15 August 2026 — 125 subscribers24 August 2026 — 123 subscribers31 August 2026 — 119 subscribers7 August 202631 August 2026
6 measurements spanning 23 days, net -7. 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 118–128 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 03:43119-4
24 Aug 2026, 03:27123-2
15 Aug 2026, 16:47125-2
9 Aug 2026, 02:01127no change
8 Aug 2026, 12:33127+1
7 Aug 2026, 17:27126first reading

Engagement

16 posts held, back to 27 January 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
60.8%
avg views ÷ 119 subscribers
Avg views / post
72.3
3 posts measured
Reaction rate
1.67%
reactions ÷ views · ER floor
Posts in window
3
of 16 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. It is computed over the 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held16 (27 January 20268 August 2026)
Views total217
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 02: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

322 reactions across 12 posts, in 21 distinct kinds. The most used accounts for 10.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52963661167953423443510.9%
custom 5298674343889362083257.76%
custom 5377624540098617403237.14%
custom 5323595565206886255226.83%
custom 5300939702914796640206.21%
custom 5323793524544525263206.21%
custom 5346251363074460554206.21%
custom 5321050204378523377195.90%
custom 5321374955445710893175.28%
custom 5336978477142794586175.28%
custom 5300879693631737383164.97%
custom 5460718683963826562154.66%
custom 5327994552315845360134.04%
custom 5434101607694365339134.04%
custom 5321382974149651055123.73%
custom 5201665489532638627103.11%
custom 5301077352321667587103.11%
custom 519966239839016320272.17%
custom 532822504173578770151.55%
custom 529873027295349137420.621%
1 further kind10.311%

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

Measured over the 16 most recent posts we hold, published 27 January 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.

Telegram Stars

Stars received
46
across the posts below
Posts paid on
10
of 15 we hold a reading for · 67%
Most on one post
11
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @vas1lievich. 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 16 most recent posts we hold for this entry, published 27 January 2026 to 8 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

6 Aug 2026, 19:28 UTC56 views3 reactionsread 9 August 2026

сильно жду зиму,надоело ваше лето 😡

custom 53279945523158453603

4 Aug 2026, 01:24 UTC124 views0 reactions1 Starread 9 August 2026
Video message

Video message, posted without a caption

1 Aug 2026, 19:05 UTC131 views23 reactions11 Starsread 9 August 2026
Photo

Photo, posted without a caption

custom 520166548953263862710custom 51996623983901632027custom 53462513630744605546

1 Aug 2026, 12:03 UTC123 views17 reactions1 Starread 9 August 2026
Photo

Photo, posted without a caption

custom 53462513630744605545custom 53776245400986174035custom 53279945523158453604custom 53282250417357877012custom 53864022850205461821

29 Jul 2026, 21:44 UTC203 views29 reactions10 Starsread 9 August 2026
Photo

готов стать папой,привожу домой деньги ❓

custom 537762454009861740311custom 53462513630744605549custom 53279945523158453606custom 53282250417357877013

24 Jul 2026, 20:05 UTC275 views26 reactions3 Starsread 9 August 2026
Photo

Photo, posted without a caption

custom 52963661167953423449custom 53237935245445252637custom 53009397029147966406custom 54341016076943653392custom 53235955652068862551custom 53369784771427945861

22 Jul 2026, 16:08 UTC302 views32 reactions6 Starsread 9 August 2026
Photo

04.04.25 🚶

custom 54341016076943653397custom 53010773523216675875custom 54607186839638265624custom 52986743438893620833custom 53235955652068862553custom 53237935245445252633custom 52963661167953423442custom 53008796936317373832

21 Jul 2026, 18:33 UTC266 views6 reactions1 Starread 9 August 2026
Video message

Video message, posted without a caption

custom 53009397029147966402custom 53235955652068862551custom 53237935245445252631custom 53369784771427945861custom 54607186839638265621

21 Jul 2026, 12:25 UTC268 views35 reactions10 Starsread 9 August 2026
Photo

ты можешь быть для кого то домом, но это не значит, что он не сожжет его

custom 532359556520688625510custom 52963661167953423446custom 53237935245445252635custom 54607186839638265625custom 53009397029147966403custom 53010773523216675873custom 54341016076943653392custom 53369784771427945861

12 Jul 2026, 20:52 UTC518 views49 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 529636611679534234412custom 533697847714279458610custom 52986743438893620839custom 53008796936317373839custom 54607186839638265625custom 53009397029147966404

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

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

“vsl” (@vas1lievich), 119 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/vas1lievich.

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.