Канал захвачен Ларисой долиной, артов больше не будет ахахаха #щп
custom 541371508586240257911

Channel
@Vikuui_chek
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
57subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002519370479 |
|---|---|
| Type | Channel |
| Username | @Vikuui_chek |
| Description | 𝒟обро п᥆жᥲл᥆вᥲть в кᥲнᥲлл!! :3 Лᥙ4кᥲ: @VaTochkA_Chekk П⍴᥆г᥆л᥆ᥴ᥆вᥲть зᥲ кᥲнᥲл: https://t.me/boost/Vikuui_chek Ан᥆н: http://t.me/anonaskbot?start=8s9hl XD |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Vikuui_chek |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 13:15 | 57 | no change |
| 10 Aug 2026, 13:04 | 57 | first reading |
17 posts held, back to 27 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 1 pageof 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. It is computed over the 15 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 17 (27 July 2026 – 7 August 2026) |
| Views total | 821 |
| Reactions total | 125 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 13:15 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 10 August 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.
125 reactions across 15 posts, in 4 distinct kinds. The most used accounts for 34.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5413715085862402579 | 43 | 34.4% | |
| custom 5406704539594164577 | 42 | 33.6% | |
| custom 5352915966906885731 | 31 | 24.8% | |
| custom 5407003993303977140 | 9 | 7.20% |
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 areTelegram’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 15 of the 17 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 125reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 27 July 2026 to 7 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.
Канал захвачен Ларисой долиной, артов больше не будет ахахаха #щп
custom 541371508586240257911
Video message, posted without a caption
custom 54067045395941645775custom 53529159669068857312
Кину вам процесс, лол #арт
custom 54067045395941645778custom 54137150858624025792custom 54070039933039771401
Ну и если вы добьете мне до сентября 60 подписчиков, нарисую тот самый большой арт #щп
custom 54137150858624025796
Приветт, я возьму мини рест на несколько дней или побольше, ведь я, хочу поэкспериментировать над стилем XD #полуинфо
custom 54137150858624025796
𝅄ׄ 𓈒 п⍴ᥙвᥱтт ო᥆ᥙ ᥊᥆⍴᥆шᥙᥱ^^ 🫧 Сегодня в 15:45 будет рубрика под названием - "вопрос - ответ" Вы можете спрашивать все что угодно, даже личное <33 Я буду рада каждому вопросу!! 💉 ────୨ৎ──── 𝅄ׄ Бᥡдᥙ ждᥲть вᥲшᥙ᥊ в᥆п⍴᥆ᥴᥙк᥆вв ^_^ 🎐 #инфо ☆⋆。𖦹°‧★ 🪽
custom 53529159669068857317custom 54067045395941645773custom 54137150858624025792custom 54070039933039771401
𝅄ׄ 𓈒◡ 𝐻ᥲ𝗍sᥙᥒᥱ ოіkᥙ 🎐 𝒫езультат мне очень понравился <33 ────୨ৎ──── ^_^ 𝅄ׄ 𝒯᥆льк᥆ п᥆ᥴო᥆т⍴ᥙтᥱ, кᥲкᥲя жᥱ ᥆нᥲ ოᥙлᥲя!! 🫧 #арт (´-﹃-`) ᶻ 𝗓 𐰁 🪽
custom 540670453959416457710custom 54137150858624025793custom 54070039933039771402
Ракетка, ракетка, летит к нам конфетка✌🏻❤️🩹 #щп
Sticker, posted without a caption
custom 54070039933039771402
𝅄ׄ 𓈒◡ 𝒞ᥲ⍴𝗍ᥲіᥒ 🫧 Фу, в архив за красоту ────୨ৎ──── ^_^ 𝅄ׄ 𝒦ᥲк жᥱ я зᥲᥱбᥲлᥲᥴь нᥲд ф᥆н᥆ო.. 💉 #арт ☆⋆。𖦹°‧★ 🎐
custom 54137150858624025798custom 54067045395941645772custom 54070039933039771401
Пока у меня не было зарядки, что бы заряжать телефон, я посмотрела все серии технолайка, мне стало жалко капитана 😭😭✌🏻 #щп
custom 53529159669068857316
Фу август #щп
custom 53529159669068857316custom 54067045395941645772
Showing the 12 most recent of 17 posts we hold for @Vikuui_chek. 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.
Citation-graph rank — 392,388 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“[Рест] 𝅄ׄ 𓈒◡ 𝒱іkᥙᥙіXD「🪽」” (@Vikuui_chek), 57 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Vikuui_chek.
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.