Channel
@VILVI_1NFO
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
82subscribers
-6 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003070922738 |
|---|---|
| Type | Channel |
| Username | @VILVI_1NFO |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 10 September 2026 |
| On Telegram | t.me/VILVI_1NFO |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 15:05 | 82 | -4 |
| 19 Aug 2026, 00:11 | 86 | -2 |
| 11 Aug 2026, 19:43 | 88 | no change |
| 11 Aug 2026, 01:47 | 88 | first reading |
18 posts held, back to 30 January 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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 reactions across 4 posts, in 8 distinct kinds. The most used accounts for 25.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5384088736462030773 | 10 | 25.6% | |
| custom 5325926778965884861 | 9 | 23.1% | |
| custom 5328038107579187397 | 7 | 17.9% | |
| custom 5325898436476696592 | 3 | 7.69% | |
| custom 5348115713888384578 | 3 | 7.69% | |
| custom 5348347938475113218 | 3 | 7.69% | |
| custom 5415986260273541075 | 3 | 7.69% | |
| custom 5348305448363651430 | 1 | 2.56% |
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 4 of the 18 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 39 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 30 January 2026 to 26 July 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.
эээ, привет?? возможно мне нужно что то сказать, да? вообщем у меня нет времени и сил на вилви в данный момент, но если честно ужасно не хочется расставаться.. будущее я не вижу, но ооочень надеюсь что к нашему второму дню рождения я буду в силах дальше что то здесь делать, дай бог мне здоровья
Signed П͓̽И͓̽З͓̽Д͓̽Ю͓̽К͓̽
привет, вилви закрываются 31 июня и больше никогда не откроются
Signed П͓̽И͓̽З͓̽Д͓̽Ю͓̽К͓̽
они меня преследуют
Signed П͓̽И͓̽З͓̽Д͓̽Ю͓̽К͓̽
я может ебанулся?
Signed П͓̽И͓̽З͓̽Д͓̽Ю͓̽К͓̽
почему в анон вилви строчат китайцы
Signed П͓̽И͓̽З͓̽Д͓̽Ю͓̽К͓̽
◻️◻️◻️◻️◻️◻️◻️◻️ 🦋Сегодня у нас в гостях владелец кф @KEO1O он расскажет,о себе,и о проекте которые он создал 🎀11.03.2026 Для прочтения интервью вам нужно перейти в комментарии Интервью от арабочки
Signed П͓̽И͓̽З͓̽Д͓̽Ю͓̽К͓̽
сегодня мы поздравляем нашего владельца — кео с днем рождения!! пиздюк, желаем тебе крепкого здоровья, любви, вдохновения, благополучия, нервов и удачи во всех начинаниях. пусть каждая прожитая минута будет наполнена только положительными эмоциями и радостью. хочется поблагодарить тебя, за этот проект и любовь к участникам вилви. можете поздравить кео в комментариях, думаю, ему будут приятны поздравления.
custom 53280381075791873973custom 53259267789658848612custom 53840887364620307732custom 53481157138883845781custom 53483054483636514301custom 53483479384751132181custom 54159862602735410751
Signed emmy.
Sticker, posted without a caption
Signed П͓̽И͓̽З͓̽Д͓̽Ю͓̽К͓̽
сегодня день рождения у нашего прекрасного совладелеца - эмми! давайте все дружно поздравим её с этим праздником! эмми спасибо что остаёшься с нами уже как полтора года и помогаешь мне, я очень сильно тебя люблю и желаю всего самого лучшего, оставайся такой же умницей красавицей, не болей и не грусти от твоего любимого кео
custom 53259267789658848614custom 53280381075791873974custom 53840887364620307733custom 53258984364766965921custom 53483479384751132181custom 54159862602735410751
Signed П͓̽И͓̽З͓̽Д͓̽Ю͓̽К͓̽
Sticker, posted without a caption
Signed П͓̽И͓̽З͓̽Д͓̽Ю͓̽К͓̽
и вновь ты здесь, кажется мы видимся слишком часто.. не думаешь что это повод подружиться? сегодня @VILVI_1NFO и прекрасные @APMFM стали лучшими друзьями надеемся на долгое сотрудничество
Signed П͓̽И͓̽З͓̽Д͓̽Ю͓̽К͓̽
Sticker, posted without a caption
Signed П͓̽И͓̽З͓̽Д͓̽Ю͓̽К͓̽
Showing the 12 most recent of 18 posts we hold for @VILVI_1NFO. 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.
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.
чего хотите?
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 18 most recent posts we hold, published 30 January 2026 to 26 July 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.
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 2 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.
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“۷༏༨۷༏” (@VILVI_1NFO), 82 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/VILVI_1NFO.
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.