этот эдит лежит у меня еще с апреля👿 #vk #mn #edit scp - nastia sdt - @vasilisaleryice @tannwerx @valieshka
❤🔥10
Signed 𝗥𝗶𝗻𝗮❦︎

Channel
@vasilisaleryice
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
371subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001925013847 |
|---|---|
| Type | Channel |
| Username | @vasilisaleryice |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/vasilisaleryice |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 23:23 | 371 | -2 |
| 7 Aug 2026, 19:45 | 373 | -1 |
| 7 Aug 2026, 03:18 | 374 | first reading |
4 posts held, back to 3 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.
| Window | Rolling 30 days · latest post in window 29 July 2026 |
|---|---|
| Posts held | 4 (3 July 2026 – 29 July 2026) |
| Views total | 552 |
| Reactions total | 81 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 03:18 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.
112 reactions across 4 posts, in 24 distinct kinds. The most used accounts for 23.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 26 | 23.2% | |
| custom 5325559030981095544 | 14 | 12.5% | |
| custom 5397851332096861306 | 13 | 11.6% | |
| custom 5267138701137316535 | 12 | 10.7% | |
| custom 5359809260567953233 | 7 | 6.25% | |
| custom 5404769961770006615 | 6 | 5.36% | |
| custom 5253545237019658179 | 4 | 3.57% | |
| custom 5301133027982733386 | 4 | 3.57% | |
| custom 5402179731418295687 | 3 | 2.68% | |
| custom 5443126643948285083 | 3 | 2.68% | |
| custom 5267114228413664434 | 2 | 1.79% | |
| custom 5289995963035843018 | 2 | 1.79% | |
| custom 5375318567862431211 | 2 | 1.79% | |
| custom 5386331001448326638 | 2 | 1.79% | |
| custom 5442922199210026444 | 2 | 1.79% | |
| 💋 | 2 | 1.79% | |
| custom 5197437343337833131 | 1 | 0.893% | |
| custom 5255754366333250896 | 1 | 0.893% | |
| custom 5269496827161376747 | 1 | 0.893% | |
| custom 5300788266662919413 | 1 | 0.893% | |
| 4 further kinds | 4 | 3.57% |
Custom emoji. 18 of the rows above are 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 4 of the 4 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 112reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 3 July 2026 to 29 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.
этот эдит лежит у меня еще с апреля👿 #vk #mn #edit scp - nastia sdt - @vasilisaleryice @tannwerx @valieshka
❤🔥10
Signed 𝗥𝗶𝗻𝗮❦︎
☺️🥬🥬🥬🥬🥬💞🤩 𖣔 Поддержите канал голосами💙 #color #annashcherbakova #remini
custom 532555903098109554413❤🔥6custom 54047699617700066156custom 54021797314182956873custom 53863310014483266382💋1custom 52557543663332508961custom 52899959630358430181
Signed 𝗥𝗶𝗻𝗮❦︎
☺️оздравляю ☺️нют🤩🫶 𖣔 Поддержите канал голосами💙 #color #annashcherbakova #remini
custom 539785133209686130613❤🔥8custom 53598092605679532337custom 54431266439482850832custom 51974373433378331311custom 52899959630358430181custom 53255590309810955441custom 54429221992100264441
Signed 𝗥𝗶𝗻𝗮❦︎
Ну кошка🙏💋 𖣔 Поддержите канал голосами💙 #color #adeliyapetrosian #remini
custom 526713870113731653512custom 52535452370196581794custom 53011330279827333864❤🔥2custom 52671142284136644342custom 53753185678624312112💋1custom 52694968271613767471
Signed 𝗥𝗶𝗻𝗮❦︎
Showing the 4 most recent of 4 posts we hold for @vasilisaleryice. 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 — 131,435 of 1,549,376entries 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“𝐑𝐢𝐧𝐚𝐧𝐨𝐯𝐬𝐤𝐚𝐲𝐚༄❁” (@vasilisaleryice), 371 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/vasilisaleryice.
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.