Photo, posted without a caption
❤169😎109😁68👨💻3🦄2

Channel
@gus_vasili
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
38,126subscribers
+2,261 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001894765702 |
|---|---|
| Type | Channel |
| Username | @gus_vasili |
| Created | 15 August 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 2 times, most recently 14 November 2026 |
| On Telegram | t.me/gus_vasili |
Memes & entertainment — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @gus_vasili/8211 · this entry23 Oct 2026, 16:41 UTC | @kekanalytics/7205723 Oct 2026, 16:46 UTC | 1.00 | 5 minutes |
| @gus_vasili/8225 · this entry29 Oct 2026, 16:32 UTC | @kekanalytics/7249629 Oct 2026, 16:32 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @kekanalytics | 16 (8/8 hand-verifiable sample passed) | 0.99 | 5 minutes | this entry (14–2) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 112 comparable posts for this entry, running 31 July 2026 to 12 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
28,400 average views per post against 38,134 subscribers — an engagement rate of 74.4%. Across the 8,315 registered channels in the same cohort — 31,623–99,997 subscribers, posting mainly in Russian — the middle half sit between 5.08% and 20.8%, with a median of 10.5%.
| Window | 30 days (6 October 2026 – 5 November 2026) |
|---|---|
| Posts measured | 41 of 41 published in the window (0 exact, 41 rounded by Telegram) |
| Views totalled | 1,163,630 |
| Mature posts only | 75.8% over 40 posts read at least 24h after publication |
| Subscribers | 38,134 measured 4 November 2026 |
| Cohort | b31623:rus · 8,315 channels · p10 2.60% · p25 5.08% · p50 10.5% · p75 20.8% · p90 35.5% |
| Position in cohort | 99.266th percentile · 7.1× the cohort median |
| Uncertainty | ±0.077% of the figure, from Telegram’s rounding |
| Post language | Russian · 96.7% of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the keys clone_source · err_high, last confirmed 15 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 08:35 | 38,126 | +5 |
| 9 Nov 2026, 16:56 | 38,121 | -15 |
| 8 Nov 2026, 07:16 | 38,136 | +6 |
| 6 Nov 2026, 23:46 | 38,130 | +10 |
| 5 Nov 2026, 22:27 | 38,120 | -14 |
| 4 Nov 2026, 20:31 | 38,134 | +11 |
| 3 Nov 2026, 21:25 | 38,123 | +18 |
| 2 Nov 2026, 18:40 | 38,105 | -2 |
| 1 Nov 2026, 18:38 | 38,107 | -10 |
| 31 Oct 2026, 21:07 | 38,117 | +9 |
| 30 Oct 2026, 22:45 | 38,108 | +4 |
| 30 Oct 2026, 00:20 | 38,104 | -4 |
| 28 Oct 2026, 22:48 | 38,108 | -5 |
| 27 Oct 2026, 03:50 | 38,113 | -10 |
| 26 Oct 2026, 01:27 | 38,123 | -21 |
| 25 Oct 2026, 02:50 | 38,144 | +5 |
| 23 Oct 2026, 23:36 | 38,139 | +5 |
| 22 Oct 2026, 22:45 | 38,134 | -4 |
| 21 Oct 2026, 23:07 | 38,138 | -2 |
| 19 Oct 2026, 14:31 | 38,140 | first reading |
271 posts held, back to 31 July 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 206 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 15 November 2026 |
|---|---|
| Posts held | 271 (31 July 2026 – 15 November 2026) |
| Views total | 1,185,730 |
| Reactions total | 34,005 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Nov 2026, 09:11 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 15 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 20 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.
200,297 reactions across 270 posts, in 58 distinct kinds. The most used accounts for 39.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 79,016 | 39.4% | |
| 🤣 | 37,530 | 18.7% | |
| ❤ | 19,050 | 9.51% | |
| 😭 | 11,934 | 5.96% | |
| 👍 | 7,560 | 3.77% | |
| 💯 | 5,213 | 2.60% | |
| 👻 | 4,005 | 2.00% | |
| 😈 | 3,777 | 1.89% | |
| 😢 | 3,734 | 1.86% | |
| 👏 | 2,741 | 1.37% | |
| ❤🔥 | 2,320 | 1.16% | |
| 🦄 | 2,293 | 1.14% | |
| 😎 | 1,808 | 0.903% | |
| 🥰 | 1,752 | 0.875% | |
| 🤔 | 1,414 | 0.706% | |
| 🙈 | 1,203 | 0.601% | |
| 💔 | 1,152 | 0.575% | |
| 🔥 | 1,055 | 0.527% | |
| 🤯 | 1,042 | 0.52% | |
| 😱 | 1,036 | 0.517% | |
| 38 further kinds | 10,662 | 5.32% |
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 271 of the 271 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 200,692 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 271 most recent posts we hold, published 31 July 2026 to 15 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @gus_vasili. 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 271 most recent posts we hold for this entry, published 31 July 2026 to 15 November 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.
Telegram’s own ‘edited’ marker: 6 of 45 posts held from the last 30 days (13.3%) 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
❤169😎109😁68👨💻3🦄2
https://t.me/kekanalytics/73460 Полностью разделяю эмоции Кекенавта
😢352😭85🤣29🙉26💯10🗿7🤯5👍3
Photo, posted without a caption
💔365😭221😁90🍌11❤5🔥3😈3👌2
Русский дата-центр перебьется, он уйдет из городов в шахты, под землю. Будет питаться бурым углем, геотермальными водами — русский дата-центр готов в минуту больших печалей превратиться в дата-крота, дата-слепыша, он будет запасать на зиму всякие кэши, всякие облака мэйл.ру
🤣786❤413😁79🙈38💯18😢16😈9👻6
Photo, posted without a caption
😁790🤣204❤57🏆41💯26😎26🤝7🤔4
Ни один танкер с российским дизелем так и не попал в США — The Wall Street Journal Всего Россия отправила несколько танкеров, но по пути они изменили курс. Один из них вёз около 300 тысяч баррелей дизеля, однако вместо США отправился в Южную Америку. Всё из-за того, что американские компании опасаются юридических, санкционных и репутационных рисков, несмотря на исключение российского дизеля из санкций США, отмечает…
🤣613😁77😢67😭19👍15👌11👾9🏆8
Шутка.
🤣661😈65🌭58😁32❤6🦄6🤷♂4❤🔥1
Уже говорил, что единственное дорогое место в Китае - это макдак. Решил проверить на вокзале. Всё так - цены по китайским меркам безумные (юань равен 12 рублям). Но оцените, как выглядит меню китайского мака в туристическом месте НА АНГЛИЙСКОМ. Ну да - несколько слов на английском есть, это правда.
❤203😁165🤷♂34👀12💋5👍2🤔2🦄2
https://t.me/infantmilitario/200411 Так я узнал, что Гингрич всё ещё жив Артефакты древних
😁45🦄10👍4❤1
Photo, posted without a caption
🤣846😁114👾32😭9☃8😈5👍4🌚2
Митч Макконнелл, совершенно точно понимающий, где находится, решил не комментировать итоги мидтёрмов
👾215🤣165😢50😁8🦄5❤4🥰4☃2
Ждем когда какой-нибудь пузатый дорнийский мейстер расскажет что Сэм Тарли не разбирается в устройстве королевской гвардии (с)
😁241🤣70❤16🦄3👍2👻1💯1🗿1
Showing the 12 most recent of 271 posts we hold for @gus_vasili. 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.
@gus_vasili edited 3 posts 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 34 posts on @gus_vasili 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 poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Что означает «эффект храповика» в описании трансмиссионного механизма на странице 103?
Shares as published. No per-option vote count is published by Telegram, so none is 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 271 most recent posts we hold, published 31 July 2026 to 15 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.
Republished by 75 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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 34 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 24 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.
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.
@gus_vasili named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 31 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 77 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Гусь Василий под тополем” (@gus_vasili), 38,126 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/gus_vasili.
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.