Блейн и Хантер 💔 ЧСВВР 2х7 серия. 🔶 Блейн, Хантер, и вы, выясняете отношения. Вы выбрали Хантера. Хантер нашëл в себе силы простить вам измену. Что случилось в Ветвуд-Роке? Лига мечтателей #чтослучилосьвветвудроке #лигамечтателей #Блейн #Хантер
🔥4

Channel
@winer_9_9_9
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
9,257subscribers
-904 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002146499157 |
|---|---|
| Type | Channel |
| Username | @winer_9_9_9 |
| Description | •инфо канал - @wfinterrr •буст https://t.me/boost/winer775 •регистрация в перечне Ркн https://gosuslugi.ru/snet/685132fba294ab7e7c8a5e96 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 39 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/winer_9_9_9 |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 64% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 6 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @lagertaguides | 8 (5/8 hand-verifiable sample passed) | 1.00 | 36 minutes | @lagertaguides (8–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 159 comparable posts for this entry, running 5 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 6 channels, the one whose matching posts we hold earliest is @malecradle. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 6 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 01:47 | 9,257 | -77 |
| 9 Nov 2026, 06:46 | 9,334 | -28 |
| 5 Nov 2026, 16:39 | 9,362 | -45 |
| 2 Nov 2026, 17:45 | 9,407 | -31 |
| 31 Oct 2026, 02:51 | 9,438 | -33 |
| 28 Oct 2026, 07:44 | 9,471 | -22 |
| 25 Oct 2026, 09:48 | 9,493 | -22 |
| 22 Oct 2026, 17:49 | 9,515 | -21 |
| 19 Oct 2026, 20:52 | 9,536 | -21 |
| 17 Oct 2026, 07:28 | 9,557 | -15 |
| 14 Oct 2026, 10:55 | 9,572 | -30 |
| 10 Oct 2026, 21:20 | 9,602 | -40 |
| 4 Oct 2026, 20:59 | 9,642 | -86 |
| 25 Sept 2026, 00:19 | 9,728 | -94 |
| 15 Sept 2026, 05:38 | 9,822 | -40 |
| 11 Sept 2026, 06:21 | 9,862 | -41 |
| 6 Sept 2026, 10:41 | 9,903 | -25 |
| 2 Sept 2026, 05:17 | 9,928 | -28 |
| 29 Aug 2026, 23:44 | 9,956 | -30 |
| 27 Aug 2026, 01:42 | 9,986 | first reading |
250 posts held, back to 5 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 65 pages of 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 91 of 105 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 250 (5 August 2026 – 17 November 2026) |
| Views total | 17,569 |
| Reactions total | 495 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 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 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 143 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.
1,251 reactions across 204 posts, in 16 distinct kinds. The most used accounts for 41.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 515 | 41.2% | |
| 🔥 | 181 | 14.5% | |
| custom 5276190233044480974 | 152 | 12.2% | |
| custom 5276322045590795651 | 80 | 6.39% | |
| ❤🔥 | 79 | 6.31% | |
| 😍 | 72 | 5.76% | |
| 🥰 | 41 | 3.28% | |
| 🤣 | 31 | 2.48% | |
| custom 5337046573849272898 | 30 | 2.40% | |
| 🍓 | 25 | 2.00% | |
| 🗿 | 22 | 1.76% | |
| 🌚 | 15 | 1.20% | |
| 💔 | 5 | 0.4% | |
| 🍌 | 1 | 0.08% | |
| 💯 | 1 | 0.08% | |
| 🤩 | 1 | 0.08% |
Custom emoji. 3 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 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 204 of the 250 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,251 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 250 most recent posts we hold, published 5 August 2026 to 17 November 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.
Telegram’s own ‘edited’ marker: 1 of 105 posts held from the last 30 days (0.952%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Блейн и Хантер 💔 ЧСВВР 2х7 серия. 🔶 Блейн, Хантер, и вы, выясняете отношения. Вы выбрали Хантера. Хантер нашëл в себе силы простить вам измену. Что случилось в Ветвуд-Роке? Лига мечтателей #чтослучилосьвветвудроке #лигамечтателей #Блейн #Хантер
🔥4
Блейн и Кайл 💔 ЧСВВР 2х3 серия. 🔶 Драка Блейна и Кайла из-за вас. Ваши отношения с Кайлом закончены. Что случилось в Ветвуд-Роке? Лига мечтателей #чтослучилосьвветвудроке #лигамечтателей #Блейн #Кайл
🔥4
Блейн и Айзек 💔 ЧСВВР 2х3 серия. 🔶 Айзек застукал вас с Блейном. Ваши отношения с Айзеком закончены. Что случилось в Ветвуд-Роке? Лига мечтателей #чтослучилосьвветвудроке #лигамечтателей #Блейн #Айзек
🔥4
Ренди ❤ ЧСВВР 1х1 серия. 🔶 Выбор: Соблазнить Ренди. (60 изумрудов) 🍓🌶Интимная сцена. 2х6 серия. 🔶 Выбор: Что нас увидят ваши коллеги? (90 изумрудов) 🍓🌶Интимная сцена + кат-сцена. Что случилось в Ветвуд-Роке? Лига мечтателей #чтослучилосьвветвудроке #лигамечтателей #Ренди
🔥4
Кин ❤ МЗХ 3х7 серия. 🔶 Выбор: Считаю. (110 молний) 🍓🌶 Интимная сцена + кат-сцена. Вы необходимы Кину как воздух. Меня зовут Хоуп Истории другого мира #Менязовутхоуп #историидругогомира #Кин
🔥4
Кин ❤ МЗХ 3х6 серия. 🔶 Выбор: Замереть. (67 молний) Кин знает, как остудить ваш пыл. 3х7 серия. 🔶 Выбор: Поцеловать по-настоящему. (56 молний) Сцена поцелуя. Меня зовут Хоуп Истории другого мира #Менязовутхоуп #историидругогомира #Кин
❤4
🔔#новости_пкр СКАНДАЛ В КР: сценаристку «Рождённого Тенью» Маришку уволили из КР после слива её жёстких высказываний. В сеть слили переписки Маришки за 2025 год из одного публичного чата. Вычислять даже не пришлось: автор сидела в официальных чатах КР с того же самого личного аккаунта. Внутри оказался настоящий комбо-набор на моментальную отмену в любой интернациональной компании: 🔴Жёсткая гомофобия (и это при т…
🌚7
❤️❤️❤️❤️❤️❤️❤️ ❤️❤️ ❤️❤️❤️❤️❤️ ♥️♥️♥️♥️♥️♥️♥️♥️♥️♥️ #Бертран #Этьен #Гаспар #Аксель #Особнякнахолме #Лагерта
🔥8
🔔🔔🔔 Друзья! Мы планируем выпустить обновление до конца дня в воскресенье, 22 ноября.
Юджин Бакстер ❤ ЧСВВР 2х4 серия. 🔶 Выбор: Позвонить Юджину Бакстеру. (60 изумрудов) Разговор. 2х5 серия. 🔶 Выбор: Ответить на поцелуй офицера. (90 изумрудов) Сцена поцелуя + кат-сцена. Вы дали понять Юджину, что он вам небезразличен. #чтослучилосьвветвудроке #лигамечтателей #Юджин #Бакстер
❤4🍌1
Юджин Бакстер ❤ ЧСВВР 1х8 серия. 🔶 Выбор: Остаться в баре. (90 изумрудов) 🍓🌶Интимная сцена + кат-сцена. 2х8 серия. 🔶 Выбор: Поехать к Юджину. (130 изумрудов) 🍓🌶Интимная сцена + кат-сцена. Вас с офицером Бакстером связывает нечто сильнее обычной симпатии. Что случилось в Ветвуд-Роке? Лига мечтателей #чтослучилосьвветвудроке #лигамечтателей #Юджин #Бакстер
custom 52761902330444809744
Джеймс ❤ МЗХ 3х5 серия. 🔶 Выбор: Обнять его. (36 молний) Ваша связь с Джеймсом стала крепче. 🔶 Выбор: Иди ко мне. (75 молний) Джеймс всегда будет рядом + кат-сцена. 3х7 серия. 🔶 Выбор: Замереть. (Сцена глазами Хоуп) (54 молнии) Вы с Джеймсом отдалились, но он всë ещë продолжает любить вас. 🔶 Выбор: Замереть. (Сцена глазами Джеймса) (54 молнии) Вы с Джеймсом отдалились, но он всë ещë продолжает любить вас. 🔶 Вы…
custom 52761902330444809742
Showing the 12 most recent of 250 posts we hold for @winer_9_9_9. 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.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“W𝘪𝘯𝘵𝘦𝘳|𝘳𝘤” (@winer_9_9_9), 9,257 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/winer_9_9_9.
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.