свадьба от . . . вестл🗝 🤍➕ условия участия 1. подписка на инфо без дальнейшей отписки 2. рт в активный канал 3. скинуть под пост доки с юзом ( без моно шрифта ) ☺️ак играть ? один игрок становится женихом , остальные невестами. У каждой невестки есть свой индивидуальный номер. Жених анонимно задает вопрос , а невесты так же анонимно отвечают на него. Жених выбирает тот ответ , который ему не понравился , жених с этим…

Channel
iɳӻᴏ
@vestl_XwX
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
341subscribers
+218 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003152934027 |
|---|---|
| Type | Channel |
| Username | @vestl_XwX |
| Created | Between 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/vestl_XwX |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 02:24 | 341 | +147 |
| 9 Aug 2026, 10:51 | 194 | +71 |
| 9 Aug 2026, 03:03 | 123 | no change |
| 8 Aug 2026, 15:45 | 123 | first reading |
Engagement
10 posts held, back to 8 August 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 · 30 days
- 53.1%
- avg views ÷ 341 subscribers
- Avg views / post
- 181
- 10 posts measured
- Reaction rate
- 40.1%
- reactions ÷ views · ER floor
- Posts in window
- 10
- of 10 held
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 8 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 10 (8 August 2026 – 8 August 2026) |
| Views total | 1,812 |
| Reactions total | 632 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 03:03 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.
Reaction mix
632 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 26.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5344044265280397043 | 167 | 26.4% | |
| 👻 | 163 | 25.8% | |
| custom 5355280105885166495 | 157 | 24.8% | |
| 🕊 | 145 | 22.9% |
Custom emoji. 2 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 8 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 632reactions 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 8 August 2026 to 8 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.
Recent posts
Sticker, posted without a caption
ᴛуᴛ ʙы ⲙ᧐жᥱᴛᥱ ᥰρᥱд᧘᧐жᥙᴛь ʙᤋ ᥰдᥰ / ⲙью ᥲκᴛуᥲ᧘ьн᧐ ʙᥴᥱᴦдᥲ !🤩🎀
🕊26👻25custom 534404426528039704324custom 535528010588516649517
Sticker, posted without a caption
custom 53440442652803970439custom 53552801058851664959🕊8👻5
ураа , 100 пдп !!🤩
custom 534404426528039704326custom 535528010588516649522👻20🕊12
y᧐ᥙr ᧐ρiᥒi᧐ᥒ ᥲδ᧐ᥙᴛ ⲙᥱ
👻37custom 534404426528039704334custom 535528010588516649533🕊28
Sticker, posted without a caption
👻7🕊7custom 53552801058851664956custom 53440442652803970433
🎀🔡ɭσѵε ɭʝʂʈ 🤩 𑣲⋆@ шио @ кириешка ˚.
custom 535528010588516649535custom 534404426528039704333👻31🕊27
Sticker, posted without a caption
custom 534404426528039704310custom 535528010588516649510🕊8👻6
🤩estl 🤍🪦🤩🤩🤩 🤩 🤩𝘦𝘯𝘧𝘱 🤩 сх2со7сп9 🤩🤩🤩🤩inks . . . 🤩🤩🤩 dm shitpost 🤩🤩🤩 anon
👻32🕊29custom 534404426528039704328custom 535528010588516649525
Showing the 10 most recent of 10 posts we hold for @vestl_XwX. 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
Citation-graph rank — 331,432 of 1,480,975entries 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.
Forward network
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.
Mentions
Named by 3 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.
Cite this entry
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“iɳӻᴏ” (@vestl_XwX), 341 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/vestl_XwX.
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.