зоркому благодарность за 📸 👈
custom 526054106013999086850custom 526065229979295733916custom 525829220237890203815

Channel
@vnicai
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
5,205subscribers
+317 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001779050185 |
|---|---|
| Type | Channel |
| Username | @vnicai |
| Created | 8 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/vnicai |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 20:17 | 5,205 | +25 |
| 5 Sept 2026, 11:58 | 5,180 | +7 |
| 1 Sept 2026, 14:04 | 5,173 | +24 |
| 29 Aug 2026, 09:48 | 5,149 | +29 |
| 26 Aug 2026, 01:19 | 5,120 | +17 |
| 23 Aug 2026, 07:17 | 5,103 | +23 |
| 20 Aug 2026, 03:58 | 5,080 | +23 |
| 17 Aug 2026, 09:24 | 5,057 | +28 |
| 13 Aug 2026, 07:58 | 5,029 | +36 |
| 10 Aug 2026, 16:41 | 4,993 | +63 |
| 8 Aug 2026, 03:20 | 4,930 | +42 |
| 7 Aug 2026, 09:31 | 4,888 | no change |
| 7 Aug 2026, 09:20 | 4,888 | first reading |
10 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 8 pages 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 10 posts for this entry, the most recent from 11 August 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.
1,497 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 28.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5260652299792957339 | 432 | 28.9% | |
| custom 5260375094013738594 | 429 | 28.7% | |
| custom 5260541060139990868 | 331 | 22.1% | |
| custom 5258292202378902038 | 305 | 20.4% |
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 10 of the 10 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 1,497 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 31 July 2026 to 11 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @vnicai. 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 10 most recent posts we hold for this entry, published 31 July 2026 to 11 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.
зоркому благодарность за 📸 👈
custom 526054106013999086850custom 526065229979295733916custom 525829220237890203815
🤩🤩🤩🐈⬛ ...вот это да 🫳 всем отдельно и за каждого спаси Бог! 4 года назад и подумать не мог что столько будет нас
custom 5258292202378902038111custom 526037509401373859430custom 526054106013999086826
клеюсь с телескопической палки
custom 526065229979295733988custom 526037509401373859436custom 525829220237890203823custom 52605410601399908686
прямое включение из города 📍Выборг на связи агенты под прикрытием
custom 5260652299792957339105custom 526037509401373859445custom 525829220237890203838custom 52605410601399908684
Томатик приезжал вот
custom 5260375094013738594105custom 526065229979295733935custom 526054106013999086830custom 52582922023789020386
будничное
custom 526065229979295733983custom 526037509401373859439custom 525829220237890203827custom 52605410601399908684
рубрика вечерние чтения 📓2Кор 5:17-21: "Итак, кто во Христе, тот новая тварь; древнее прошло, теперь все новое. Все же от Бога, Иисусом Христом примирившего нас с Собою и давшего нам служение примирения, потому что Бог во Христе примирил с Собою мир, не вменяя людям преступлений их, и дал нам слово примирения. Итак мы — посланники от имени Христова, и как бы Сам Бог увещевает через нас; от имени Христова просим: …
custom 526065229979295733931custom 526037509401373859413custom 52605410601399908689custom 52582922023789020386
в гости к батьку ездил, на воротах нарисовал
custom 5260541060139990868142custom 526037509401373859456custom 525829220237890203842custom 526065229979295733914
OTN CREW (MESTOR) BIRK (OTN) НИКИТОС ВНИЦАЙ большой коллаб в питере
custom 526054106013999086858custom 526037509401373859418custom 526065229979295733915custom 52582922023789020389
тот самый тоннель в Ереване
custom 526037509401373859487custom 526065229979295733945custom 525829220237890203828custom 52605410601399908682
Showing the 10 most recent of 10 posts we hold for @vnicai. 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.
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 5 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“ВНИЦАЙ †=♡” (@vnicai), 5,205 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/vnicai.
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.