Channel
@Romanceclub_otp
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
13,271subscribers
-24 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001795089584 |
|---|---|
| Type | Channel |
| Username | @Romanceclub_otp |
| Description | 💎 Бот для вопросов и спойлеров: @Romance_club_otpBot 💎 Поддержать донатом: https://dzen.ru/id/64ea5b9b2c60877b30133f76?donate=true 💎 Дзен: https://dzen.ru/id/64ea5b9b2c60877b30133f76?clid=1400 💎 Поддержать канал: https://t.me/boost/Romanceclub_otp |
| Created | 1 February 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/Romanceclub_otp |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 29% 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 why it has no browse page of its own yet.
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 word for word on 1 other registered channel. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @official_romanceclub/61584 Aug 2026, 12:59 UTC | @Romanceclub_otp/60675 · this entry4 Aug 2026, 13:01 UTC | 1.00 | 72 seconds |
| @official_romanceclub/61645 Aug 2026, 12:59 UTC | @Romanceclub_otp/60689 · this entry5 Aug 2026, 13:05 UTC | 1.00 | 6 minutes |
| @official_romanceclub/61766 Aug 2026, 13:00 UTC | @Romanceclub_otp/60695 · this entry6 Aug 2026, 13:10 UTC | 1.00 | 11 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @official_romanceclub | 9 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | @official_romanceclub (9–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 3 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 14 comparable posts for this entry, running 4 August 2026 to 7 August 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.
Across the whole group of 2, the earliest publisher we hold is @official_romanceclub. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 7 August 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’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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 |
|---|---|---|
| 12 Aug 2026, 09:58 | 13,271 | -1 |
| 11 Aug 2026, 10:48 | 13,272 | -4 |
| 10 Aug 2026, 12:17 | 13,276 | -3 |
| 9 Aug 2026, 14:11 | 13,279 | -4 |
| 8 Aug 2026, 15:14 | 13,283 | -4 |
| 7 Aug 2026, 15:57 | 13,287 | -1 |
| 6 Aug 2026, 18:43 | 13,288 | -7 |
| 6 Aug 2026, 09:15 | 13,295 | no change |
| 6 Aug 2026, 09:07 | 13,295 | first reading |
64 posts held, back to 4 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 16 pagesof 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 12 August 2026 |
|---|---|
| Posts held | 64 (4 August 2026 – 12 August 2026) |
| Views total | 112,223 |
| Reactions total | 4,976 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 11:56 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 12 August 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 14 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.
4,976 reactions across 64 posts, in 20 distinct kinds. The most used accounts for 45.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2,282 | 45.9% | |
| custom 5472388672747762443 | 539 | 10.8% | |
| custom 5190942764375766227 | 452 | 9.08% | |
| 🤣 | 395 | 7.94% | |
| ❤🔥 | 349 | 7.01% | |
| custom 5431779344647221684 | 325 | 6.53% | |
| 💯 | 120 | 2.41% | |
| 😁 | 118 | 2.37% | |
| custom 5431546196642525002 | 114 | 2.29% | |
| 💔 | 70 | 1.41% | |
| 🥰 | 46 | 0.924% | |
| 😭 | 43 | 0.864% | |
| 🤔 | 30 | 0.603% | |
| 🙏 | 24 | 0.482% | |
| 😱 | 23 | 0.462% | |
| 💋 | 17 | 0.342% | |
| 🔥 | 12 | 0.241% | |
| 😍 | 10 | 0.201% | |
| 👍 | 6 | 0.121% | |
| 👏 | 1 | 0.02% |
Custom emoji. 4 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 64 of the 64 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 4,976reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 64 most recent posts we hold, published 4 August 2026 to 12 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.
Предлагаем взглянуть на ещё одно игровое предупреждение! ⚠️ Кажется, здесь наша главная героиня определяется с выбором фаворита... Как думаете, из какой истории это уведомление?💕
❤5custom 54723886727477624431
🟣🟣🟣🟣🟣🟣🟣🟣🟣🟣 По традиции предупреждаю: после выхода обновления на канале будут спойлеры без блюра!
❤88custom 543154619664252500228custom 543177934464722168414🤔2custom 51909427643757662272
Внебрачный сын Анубиса и Дина из ЭС выглядит прекрасно
custom 5472388672747762443135❤20custom 543177934464722168410🤣9custom 51909427643757662273
Он так долго ждал встречи с тобой... И, кажется, отпускать свою главную жертву уже не собирается. Но разве это когда-нибудь тебя останавливало? Встречайте нового фаворита «Аверрис: Дитя Разлома» — познакомиться с ним сможете уже в грядущем обновлении!
custom 519094276437576622758
🪄Пора заглянуть в будущее! Перед вами фрагмент кат-сцены из предстоящего обновления. Какую историю украсит этот арт? Делитесь своими теориями ниже! 💬
custom 519094276437576622734custom 54317793446472216846❤3
🔔🔔🔔 Друзья! Мы планируем выпустить обновление в течение дня в воскресенье, 16 августа.
❤56😭43👍4
Говорили вроде о 3 ГГ? По центру, надеюсь, не она 🫨
😁109🤣75❤6custom 54723886727477624432
Вот это их «О красном» меня триггернуло, конечно... Выглядит пока хорошо. Я рада, что Винси полегче стало, хотя я думала, что она всё-таки подольше отдохнёт
❤🔥119❤25custom 543177934464722168411💋4🙏1
Сестринские узы, жажда мести и багровые стены Имперского города... Перед её глазами всплывает алый, но что это — кровь павших или клетка, в которую она входит? Винси, автор «Сердца Треспии» и «Бездушной», возвращается с новой историей: «О красном и безмолвном море». Насладиться первыми главами и познакомиться с новыми героями можно будет уже в ближайшем обновлении Клуба Романтики.
❤🔥72❤10
Последняя встреча уже так близка — главный брахман дюжины Рам Дубей из истории «Кали — Пламя Сансары» оставил это признание. Просьба выжить и быть рядом — всё, что нужно для горячего тигриного сердца. Теперь нет выбора: только победа и возвращение в объятия Рама. 🕌
❤39custom 54317793446472216849
⌛️Августовское обновление всё ближе! Заполняем ожидание приятным интригующим знакомством: перед вами персонаж из будущих серий. Как думаете, кто это и в какой истории нам предстоит с ней встретиться? Пишите свои догадки в комментариях! ✍️
❤37
#кр_тикток_otp Да, я планирую ещё больше задолбать вас ИИ- версией ЛИ Автор #ли
❤90❤🔥30👍2
Showing the 12 most recent of 64 posts we hold for @Romanceclub_otp. 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 — 902,431 of 1,151,006entries 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Мальчик Владик не одобрит 😈” (@Romanceclub_otp), 13,271 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Romanceclub_otp.
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.