Channel
@Romaii_Zz
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
28subscribers
-82 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003922302511 |
|---|---|
| Type | Channel |
| Username | @Romaii_Zz |
| Created | Between 1 April 2026 and 29 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 2 times, most recently 10 November 2026 |
| On Telegram | t.me/Romaii_Zz |
Marketing & affiliate — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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 2 other registered channels. This entry also sits inside a group of 4 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 |
|---|---|---|---|---|
| @wegjks | 8 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | this entry (8–0) |
| @oshi_no_ko_ai2025 | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | this entry (6–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 5 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 16 comparable posts for this entry, running 29 July 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.
Recorded under the keys clone_mutual · clone_source, last confirmed 11 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 4 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.
1 more channel is in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 10:55 | 28 | -2 |
| 18 Oct 2026, 23:09 | 30 | +3 |
| 12 Oct 2026, 22:57 | 27 | -4 |
| 2 Oct 2026, 13:55 | 31 | -6 |
| 17 Sept 2026, 10:16 | 37 | -1 |
| 8 Sept 2026, 22:02 | 38 | -7 |
| 30 Aug 2026, 18:47 | 45 | -12 |
| 24 Aug 2026, 00:14 | 57 | -44 |
| 16 Aug 2026, 07:24 | 101 | -8 |
| 9 Aug 2026, 07:45 | 109 | no change |
| 8 Aug 2026, 18:10 | 109 | -1 |
| 8 Aug 2026, 11:31 | 110 | first reading |
16 posts held, back to 29 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 page of 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 16 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
🌟** ✶// 🌟pеꭑя п🤩uшлᨵׁׅׅ...🤩🤩 🤩вой канал нуждается в этой папке, ведь она даёт огромный приход за маленький срок!!𖥨 ¸،، ▸ ִֶָ 🌸 🌟 ссылку ᨵׁׅׅст𐐼вляю лишь на ч𐐼с!!! https://t.me/+DhK3E6id86EyY2Qy https://t.me/+DhK3E6id86EyY2Qy {🌷} 𑄈тзывы прих𑄈да 𑄈т папки: @babbaykkaa
💭 ּ ֗ ִ ּ ۪ 🤍р𝓞чнᦅ!!! ℬ этꭷm ч𐐼те ∂࡙ел𐐼ют прuхꭷ∂࡙ п∂࡙п. ϐִ к𐐼н𐐼лы!! +5О ϐִсᥱг𑄝͏ з𐓟ִ дᥱнь, эт𐓟ִ п𐐼пк𐓟ִ тϐִ𑄝͏թֺuт чყִ∂࡙ᥱс𐓟ִ 𓏲࣪ ֗ ִ🤩🤩 ִֶָ ּ ֗ ִ ּ ۪💭 @b𝓐b𐐼ყִk𐓟ִfִ࣪ᦒ᩠ׂׅldᥱr🤩🤩 @b𝓐b𐐼ყִk𐓟ִfִ࣪ᦒ᩠ׂׅldᥱr @b𝓐b𐐼ყִk𐓟ִfִ࣪ᦒ᩠ׂׅldᥱr 🥹ск𑄝͏թֺᥱй ִ ϐִстყִп𐓟ִй тყִ∂࡙𐓟ִ!!! 🍎🎀12/13 ყִжᥱ з𐐼шлu. 🎀
🗯☺️тот чат нужен твоему каналу!! П𝖮Ч𝖤𝖬U??💭 🤩🤩 nрuх𑄈д от +1ОО пдп. ꒰𑄈тзывы꒱ 🤩🤩 nр𑄈стые усл𑄈вuя чт𑄈бы n𑄈nасть в nаnку 🌟 ⌒ׅ⌒ׄ 00 ссылка действует лишь один час, успей зайти!!🪷 @b𐐼b𐐼ყִk𐐼f✶lder @b𐐼b𐐼ყִk𐐼f✶lder @b𐐼b𐐼ყִk𐐼f✶lder @b𐐼b𐐼ყִk𐐼f✶lder (кликабельно//)
── ◟ ۫ ִℳ𐐫ж݁ет 𐐫на u 𝟭О/𝟭О. . Ꮺ ࣪⊹݁݁ ִ🗯ゲ! ٬٬ он𐐼 ִ не вст݁упил𐐼 ִв эту݁ ִ прекр݁𐐼сную ִ п𐐼݁пку ִ... ᯽ 𐐫݁н𐐼 𝟭О݁/𝟭О . . ¿?
#question🤩 может уже пора вступить в этот чат, где делают огромный приход за короткое время?? 🌟ᦅнечнᦅ!!! ведь . . дᦅступ в неё ограничен 🤩 https://t.me/+DhK3E6id86EyY2Qy https://t.me/+DhK3E6id86EyY2Qy ссылку скᨵׁׅׅрᨵׁׅׅ уд𐐼лят, успей з𐐼йти!! ❤️ — отзывы прихода и папки:: @babbaykkaa
૮꒰๑ˊᜊˋ๑꒱ა . . – 🔤щешь прuхꪮд подпuсчuкꪮв в канал, нꪮ нuкак не пꪮлучалꪮсь набрать аудuтꪮрию？ в этом чате . . ты . . сможешь набрать подписчиков! https://t.me/+DhK3E6id86EyY2Qy https://t.me/+DhK3E6id86EyY2Qy https://t.me/+DhK3E6id86EyY2Qy 🤩ꪮветую скꪮрей зайти в чат, ведь ссылку скꪮрꪮ удалят!! 🤩
── ◟ ۫ ִℳ𐐫ж݁ет 𐐫на u 𝟭О/𝟭О. . Ꮺ ࣪⊹݁݁ ִ🗯ゲ! ٬٬ он𐐼 ִ не вст݁упил𐐼 ִв эту݁ ִ прекр݁𐐼сную ִ п𐐼݁пку ִ... ᯽ 𐐫݁н𐐼 𝟭О݁/𝟭О . . ¿?
࿙࿚ · ࿙࿚ · ࿙࿚ · ࿙࿚ · ࿙࿚ · ࿙࿚ · ࿙࿚ · ࿙࿚ · ࿙࿚ 𖥔 ִˑ 𖥻 ִ ۫ — ☺️айⲇена λучшая ᥰаᥰка +🔤 ⲇλя тв𑄈ег𑄈 канаλа!¿ ➿🪷➿🪷➿🪷➿🪷➿🪷➿🪷 ⭐⭐⭐⭐— ра𝐜𝐜ыλ бęз 𝐜кама. ⭐⭐⭐⭐ — ᥰрих𑄈ⲇ 𑄈т +𝟏𝟎𝟎 ᥰⲇᥰ. ⭐⭐⭐⭐— ⲇ𑄈брые уча𝐜тники аⲇмини𝐜трация. 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 Ⳋ᧙ .⊹ — 🔤ажимай на кноᥰку ниже и 𝐜корее в𝐜тупай в ᥰаᥰку!¿
☺️а б о р • ' 🌷 / В ПАПКУ / Ⳋ᧙ .⊹ 🎀 🧩 _ : @babaykafolder ...🥹👄 🎀ηαηκα ɓαɓαύκυ🎀 — ᥙⲙᥱнн᧐ ᴛ᧐ ⲙᥱᥴᴛ᧐, ᴦдᥱ ᥰ᧐дᥰᥙᥴчᥙκᥙ ρᥲᥴᴛуᴛ. 🎀 ꒰·.ೃ🥹࿔:ກρuχ০∂ ০τ +150 ກ∂ກ.😺 𝅄 ᶻ🥹𓐍⃘ ₊˚ησɠημϲɥμӄμ ραϲτγτ ρεӷγλяρϰσ.🐍 ⋆˖ ࣪🤩!⚹︎∂σɓραя α∂ɱυʜυсτραʯυя.🕯 𝅄 ݊݊ ֶָ֢⌯꧈🪷𓏲࣪ ссылка!! :: https://t.me/+DhK3E6id86EyY2Qy ✔️// скорей заходи в чат и вступай в папку
── ◟ ۫ ִℳ𐐫ж݁ет 𐐫на u 𝟭О/𝟭О. . Ꮺ ࣪⊹݁݁ ִ🗯ゲ! ٬٬ он𐐼 ִ не вст݁упил𐐼 ִв эту݁ ִ прекр݁𐐼сную ִ п𐐼݁пку ִ... ᯽ 𐐫݁н𐐼 𝟭О݁/𝟭О . . ¿?
‼️‼️СРОЧНОО ПРИВЕДЕМ БЕСПЛАТНО 200 ПОДПИСЧИКОВ!! благодаря нашей папке к тебе польется БЕШЕНЫЙ АКТИВ❕ ждем только тебя, отзывы есть!! https://t.me/+8rstEDiAbKxmMzVi https://t.me/+8rstEDiAbKxmMzVi https://t.me/+8rstEDiAbKxmMzVi
🐈⬛ ☺️ебе уже пора заняться своим каналом . . . 🤩🤩 — у меня нету подписчиков 🤩🤩 — приход очень маленький, что мне делать? ЗН𝓐К0М0? 🤩🤩&& 🤍𑄈гд𐐼 встуn𐐼й в эту nрекр𐐼сную +О/+1ОО n𐐼nку 💭 ➿ · 💭 · ➿ · 💭 · ➿ · 💭 · ➿ · 💭 · https://t.me/+DhK3E6id86EyY2Qy https://t.me/+DhK3E6id86EyY2Qy ✨ск𑄈рее зах𑄈ди туда, ведь ссылку удалят! 13/14 зашли...
Showing the 12 most recent of 16 posts we hold for @Romaii_Zz. 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.
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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Дв0р3цкая’ Zz” (@Romaii_Zz), 28 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/Romaii_Zz.
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.