Photo, posted without a caption
custom 5431872433768404436206custom 543182378037887536863custom 543159019428751381652custom 537517447600462695913custom 521751737630357006411custom 54314345317878062888custom 53773880634942764473

Channel
@vilchinski1
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Cite this entry
19,677subscribers
+4,172 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002495361335 |
|---|---|
| Type | Channel |
| Username | @vilchinski1 |
| Description | бизнес @envy_manager vilchinski.com |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/vilchinski1 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 03:07 | 19,677 | +188 |
| 9 Nov 2026, 12:37 | 19,489 | +46 |
| 8 Nov 2026, 03:59 | 19,443 | +36 |
| 6 Nov 2026, 22:46 | 19,407 | +71 |
| 5 Nov 2026, 21:38 | 19,336 | +254 |
| 4 Nov 2026, 21:00 | 19,082 | +683 |
| 3 Nov 2026, 22:47 | 18,399 | +41 |
| 2 Nov 2026, 20:56 | 18,358 | +42 |
| 1 Nov 2026, 21:31 | 18,316 | +79 |
| 31 Oct 2026, 19:40 | 18,237 | +85 |
| 30 Oct 2026, 22:45 | 18,152 | +74 |
| 30 Oct 2026, 01:21 | 18,078 | +91 |
| 29 Oct 2026, 04:19 | 17,987 | +186 |
| 28 Oct 2026, 00:16 | 17,801 | +95 |
| 26 Oct 2026, 22:30 | 17,706 | +10 |
| 25 Oct 2026, 19:57 | 17,696 | +50 |
| 24 Oct 2026, 19:39 | 17,646 | +42 |
| 23 Oct 2026, 18:36 | 17,604 | +120 |
| 22 Oct 2026, 16:16 | 17,484 | +22 |
| 20 Oct 2026, 09:39 | 17,462 | first reading |
143 posts held, back to 1 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 74 pages of 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.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 143 (1 August 2026 – 10 November 2026) |
| Views total | 703,010 |
| Reactions total | 16,543 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 06:03 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.
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 2 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.
39,825 reactions across 140 posts, in 8 distinct kinds. The most used accounts for 31.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5431590194287513816 | 12,439 | 31.2% | |
| custom 5375174476004626959 | 7,882 | 19.8% | |
| custom 5431823780378875368 | 6,807 | 17.1% | |
| custom 5377388063494276447 | 5,826 | 14.6% | |
| custom 5431434531787806288 | 4,107 | 10.3% | |
| custom 5431872433768404436 | 2,603 | 6.54% | |
| custom 5217517376303570064 | 126 | 0.316% | |
| custom 5431656147805314406 | 35 | 0.088% |
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 141 of the 143 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 40,037 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 143 most recent posts we hold, published 1 August 2026 to 10 November 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’s own ‘edited’ marker: 2 of 45 posts held from the last 30 days (4.44%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Photo, posted without a caption
custom 5431872433768404436206custom 543182378037887536863custom 543159019428751381652custom 537517447600462695913custom 521751737630357006411custom 54314345317878062888custom 53773880634942764473
всё
custom 5431590194287513816139custom 537517447600462695940custom 543182378037887536826custom 52175173763035700649custom 54314345317878062888custom 54318724337684044363custom 53773880634942764471
https://t.me/boost/vilchinski1 плиз
custom 537738806349427644785custom 543182378037887536832custom 543159019428751381618custom 537517447600462695912custom 52175173763035700643
Photo, posted without a caption
custom 5431590194287513816311custom 543182378037887536899custom 537738806349427644767custom 537517447600462695936custom 52175173763035700644
иногда приходит осознание что я потенциально жесткий качёк
custom 5431590194287513816356custom 543182378037887536893custom 537517447600462695976custom 543143453178780628827custom 53773880634942764476custom 52175173763035700641
я x solutions
The shares total 108%, 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.
custom 5431590194287513816100custom 543182378037887536821custom 543143453178780628819custom 53751744760046269597custom 53773880634942764475custom 52175173763035700641
solutions
custom 5377388063494276447183custom 543159019428751381639custom 543143453178780628819custom 537517447600462695910custom 54318237803788753686custom 52175173763035700641
Photo, posted without a caption
custom 5431823780378875368282custom 537738806349427644781custom 537517447600462695956custom 543159019428751381620custom 54314345317878062887custom 52175173763035700641
Photo, posted without a caption
custom 5431434531787806288186custom 537738806349427644773custom 543159019428751381645custom 537517447600462695920custom 543182378037887536812custom 52175173763035700641
Photo, posted without a caption
custom 5431823780378875368201custom 543159019428751381662custom 543143453178780628838custom 537517447600462695913custom 53773880634942764477
лучшая шоверм
custom 5431590194287513816170custom 543182378037887536844custom 537738806349427644725custom 537517447600462695912
куда сходить питире
custom 5431823780378875368161custom 543143453178780628869custom 537517447600462695943custom 543159019428751381612custom 537738806349427644711
Showing the 12 most recent of 143 posts we hold for @vilchinski1. 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.
@vilchinski1 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 7 posts on @vilchinski1 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
я x solutions
The shares total 108%, 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.
?
The shares total 110%, 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.
куда пойти
The shares total 109%, 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 143 most recent posts we hold, published 1 August 2026 to 10 November 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 23 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. The 22 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“никита вильчинский” (@vilchinski1), 19,677 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/vilchinski1.
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.