Telegram RegisterThe public register of Telegram
Telegram profile photo for big_man_vasiliy

Channel

big_man_vasiliy

@big_man_vasiliy

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

2,659subscribers

+10 since we began measuring on 28 August 2026

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

Register entry

Telegram ID-1002600329326
TypeChannel
Username@big_man_vasiliy
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 August 2026
Last confirmed live16 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/big_man_vasiliy

Topic

Ecommerce storefront — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

2,6462,6592,652.528 August 2026 — 2,649 subscribers28 August 2026 — 2,649 subscribers28 August 2026 — 2,650 subscribers31 August 2026 — 2,646 subscribers4 September 2026 — 2,648 subscribers8 September 2026 — 2,659 subscribers13 September 2026 — 2,656 subscribers16 September 2026 — 2,659 subscribers28 August 202616 September 2026
8 measurements spanning 19 days, net +10. 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 2,644–2,661 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 19:182,659+3
13 Sept 2026, 04:422,656-3
8 Sept 2026, 23:422,659+11
4 Sept 2026, 00:142,648+2
31 Aug 2026, 18:062,646-4
28 Aug 2026, 18:282,650+1
28 Aug 2026, 10:002,649no change
28 Aug 2026, 09:462,649first reading

Engagement

11 posts held, back to 25 June 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
12.3%
avg views ÷ 2,659 subscribers
Avg views / post
326
2 posts measured
Reaction rate
3.07%
reactions ÷ views · ER floor
Posts in window
2
of 11 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 28 August 2026
Posts held11 (25 June 202628 August 2026)
Views total652
Reactions total20
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 10:00 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
2m 14s
Average length
13s

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

169 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 45.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥7645.0%
👍4325.4%
3420.1%
👌84.73%
😍31.78%
🤝21.18%
🤩21.18%
💯10.592%

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

Measured over the 11 most recent posts we hold, published 25 June 2026 to 28 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

28 Aug 2026, 07:30 UTC154 views8 reactionsread 28 August 2026
Video

Образы на @big_man_vasiliy Футболки унисекс с озон Леший - Белый - #2384050158 Водяной - Песочный - #3787714695 EU Nightmare - Шоколадный - #2163446019 Джинсы черные вб #522918532 Джинсы коричневые вб #155401341 Образы на @kutsenko.mary Футболки унисекс с озон Змей Горыныч - Персиковый - #3982729292 Матрёшка - Желто Оранжевый - #4893076032 Жар Птица Гжель - Белый - #2384027044 Джинсы синие вб #36138119 Джинсы коричн

🔥43👍1

22 Aug 2026, 10:11 UTC498 views12 reactionsread 28 August 2026
Video

Брюки черные #437022876 Брюки бежевые #437022878 Брюки коричневые #437022877 Рубашка белая в полоску #1218394886 Рубашка коричневая в полоску #1218427526 Рубашка голубая #931251326

🔥8👍21👌1

21 Jul 2026, 09:24 UTC≈1,110 views14 reactionsread 28 August 2026
Video

Бежевый #450815546 на мне 3XL Серый #533259552 на мне 3XL Черный #450815547 на мне 3XL Джинсы озон #1617930468 на мне 60 Брюки #978272807 на мне 60

🔥93👌2

9 Jul 2026, 11:48 UTC≈1,360 views14 reactionsread 28 August 2026
Video

Рубашка молочная #852851580 Брюки #511189733 Рубашка шоколадная #853234202 Шорты желтые #869268508 Рубашка оливковая #852851584 Шорты желтые #869268508 Рубашка черно/белая #852851587 Брюки #511189733 Рубашка голубая #853234204 Шорты желтые #869268508 Рубашка в полоску #852657395 Шорты белые #160797477 Футболка шоколадная #869467524 Шорты белые #160797477

7🔥5👍2

6 Jul 2026, 08:24 UTC≈1,120 views15 reactionsread 28 August 2026
Video

Свитшот молочный #438287946 на мне 3XL Свитшот черный #438287945 на мне 3XL Джинсы озон#1617930468 на мне 60-62 Брюки бежевые #978272807 на мне 60 Брюки шоколадные #978258445 на мне 60

🔥113👍1

5 Jul 2026, 09:19 UTC≈1,040 views12 reactionsread 28 August 2026
Video

Серый с капюшоном #WW487205 Вязанный голубой #WW541231 Лацкан голубой #WW487177 Оливковый #WW487206 Графитовый #WW487207 Белый в полоску #WW487178

6🔥3👍2🤝1

1 Jul 2026, 14:46 UTC≈1,130 views20 reactionsread 28 August 2026
Video

Верх Голубая #WW487054 Шоколад #WW487055 Оливка в полоску #WW540257 Шоколад волнистая #WW487056 Белая #WW486996 Полоска изумруд/черный #WW487057 Низ Брюки бежевые #978272807 Брюки шоколадные #978258445 Шорты #234265618

🔥9👍8😍2🤝1

29 Jun 2026, 09:32 UTC≈1,030 views17 reactionsread 28 August 2026
Video

Набор трусов #912964497

👍8🔥4👌32

28 Jun 2026, 09:41 UTC≈1,060 views18 reactionsread 28 August 2026
Photo

Фотографии из сегодняшнего обзора 🔥

👍10🔥43😍1

28 Jun 2026, 08:19 UTC≈1,020 views18 reactionsread 28 August 2026
Video

Джинсы-бананы 🔥 широкий размерный ряд до 66 размера Темно-синие WB #WW511616 OZON #4188077014 Светло-голубые WB #WW511638 OZON #2054099928 Футболки 🔥 Черная, бежевая с сайта wuzen.ru Коричневая WB #959733442

🔥13👌2🤩21

25 Jun 2026, 10:01 UTC≈1,070 views21 reactionsread 28 August 2026
Video

Шорты с озона #3932677157 мне подошел 54 размер Футболка черная с сайта wuzen.ru Поло коричневое #959733442 на мне 5XL Поло полосатое #556286905 на мне 54 Я ношу размер 58-60

👍9🔥65💯1

Showing the 11 most recent of 11 posts we hold for @big_man_vasiliy. 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.

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.

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.

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

“big_man_vasiliy” (@big_man_vasiliy), 2,659 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/big_man_vasiliy.

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.