Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝙒𝙄𝙉𝙀𝙓🍷||𝐓𝐆𝐊

Channel

𝙒𝙄𝙉𝙀𝙓🍷||𝐓𝐆𝐊

@Winex002

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

32subscribers

+0 since we began measuring on 15 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002175895156
TypeChannel
Username@Winex002
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live16 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/Winex002

Growth

3215 Aug 2026, 03:16 — 32 subscribers16 Aug 2026, 09:04 — 32 subscribers15 Aug 2026, 03:1616 Aug 2026, 09:04
2 measurements spanning 1 day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 31–33 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 09:0432no change
15 Aug 2026, 03:1632first reading

Engagement

13 posts held, back to 3 February 2026the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 13 posts for this entry, the most recent from 5 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 22s
Average length
10s

Measured directly from 8 videos 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.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
150.0%
🥰150.0%

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 2 of the 13 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 3 February 2026 to 5 June 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

5 Jun 2026, 19:34 UTC27 viewsread 15 August 2026
Photo

⌢ ○ ₊ ୨𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎୧ ₊ ○ ⌢ 🖤🖤🖤🤩🤩🤩🤩🤩🤩: Varvara Petrovich. идея является нашей, просьба отмечать при взятии. 🖤🖤🖤🖤По поводу вступления писать: @wiwnvv #новоевидео

5 Jun 2026, 17:46 UTC31 viewsread 15 August 2026

🔤🔤🔤🔤🔤🔤🔤 — 🔤ечер добрый, Товарищи! 🔤ак ваши дела? 🔤ивы ещё? 🔤 пришла вам объявить, что спустя месяца два флуд вновь возвращает свою работу. 🔤н вновь открыт для новых участников, уже добавлены новые роли, что с нетерпением вас ждут. 🔤онечно я раздумывала над тем, чтобы покончить с этим всем, но мечта добить 5 лет по-прежнему остаётся. 🔤отому, мы с нетерпением будем ждать вас! 🔤🔤🔤🔤t.me/Winex00 🔤🔤@wiwnvv

13 Apr 2026, 18:53 UTC59 views1 reactionsread 15 August 2026

🔤🔤🔤🔤🔤🔤🔤 — Ребят, я просто кулич на пасху съел.

1

13 Apr 2026, 18:52 UTC58 viewsread 15 August 2026
Photo

⌢ ○ ₊ ୨𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎୧ ₊ ○ ⌢ ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ 𝑨𝑼𝑻𝑯𝑶𝑹: Melissa Dzhebisashvili. ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ По поводу вступления писать: @wiwnvv #новоевидео

13 Apr 2026, 18:50 UTC43 viewsread 15 August 2026
Photo

⌢ ○ ₊ ୨𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎୧ ₊ ○ ⌢ ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ 𝑨𝑼𝑻𝑯𝑶𝑹: Melissa Dzhebisashvili. ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ По поводу вступления писать: @wiwnvv #новоевидео

26 Mar 2026, 11:34 UTC98 viewsread 15 August 2026
Photo

⌢ ○ ₊ ୨𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎୧ ₊ ○ ⌢ ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ 𝑨𝑼𝑻𝑯𝑶𝑹: Dmitry Matveev. ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ По поводу вступления писать: @wiwnvv #новоевидео

26 Mar 2026, 06:32 UTC47 viewsread 15 August 2026
Photo

⌢ ○ ₊ ୨𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎୧ ₊ ○ ⌢ ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ 𝑨𝑼𝑻𝑯𝑶𝑹: Dmitry Matveev. ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ По поводу вступления писать: @wiwnvv #новоевидео

17 Mar 2026, 19:06 UTC76 views1 reactionsread 15 August 2026
Photo

⌢ ○ ₊ ୨𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎୧ ₊ ○ ⌢ ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ 𝑨𝑼𝑻𝑯𝑶𝑹: Dmitry Matveev. ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ По поводу вступления писать: @wiwnvv #новоевидео

🥰1

7 Feb 2026, 20:29 UTC121 viewsread 15 August 2026
Photo

⌢ ○ ₊ ୨𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎୧ ₊ ○ ⌢ ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ 𝑨𝑼𝑻𝑯𝑶𝑹: Alexander Sakov. ꒰ ♡ ꒱──⑅─── ♡ ───⑅──꒰ ♡ ꒱ По поводу вступления писать: @Wikil0 #новоевидео

Showing the 12 most recent of 13 posts we hold for @Winex002. 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 — 642,422 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.

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.

“𝙒𝙄𝙉𝙀𝙓🍷||𝐓𝐆𝐊” (@Winex002), 32 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Winex002.

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.