مێلینا دوونیایەک لە جوانی نووسین
Signed لیستــVIP

Channel
@zhian_babe_to
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
10subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001477299797 |
|---|---|
| Type | Channel |
| Username | @zhian_babe_to |
| Description | . . . منەتی مانگ و ئەستێرەکان هەڵناگرم ڕوخساری تۆ بەسە بۆ ڕوناکردنەوەی شەوانی من🧸🤍! . . @dnawsarok چەناڵەکەم . . @sarrokm |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/zhian_babe_to |
Memes & entertainment — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 11 November 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 2 other registered channels. This entry also sits inside a group of 3 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @zhian_babe_to/5915 · this entry19 Oct 2021, 11:17 UTC | @Zhian_lagal_to/1068119 Oct 2021, 11:17 UTC | 1.00 | under a minute |
| @zhian_babe_to/5929 · this entry19 Oct 2021, 16:55 UTC | @Zhian_lagal_to/1070219 Oct 2021, 16:55 UTC | 1.00 | under a minute |
| @Zhian_lagal_to/1071519 Oct 2021, 20:38 UTC | @zhian_babe_to/5940 · this entry19 Oct 2021, 20:38 UTC | 1.00 | under a minute |
| @zhian_babe_to/5957 · this entry20 Oct 2021, 10:42 UTC | @Zhian_lagal_to/1073720 Oct 2021, 10:42 UTC | 1.00 | under a minute |
| @zhian_babe_to/5976 · this entry20 Oct 2021, 18:30 UTC | @Zhian_lagal_to/1076320 Oct 2021, 18:30 UTC | 1.00 | under a minute |
| @Zhian_lagal_to/1109928 Oct 2021, 20:41 UTC | @zhian_babe_to/6148 · this entry28 Oct 2021, 20:41 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Zhian_lagal_to | 7 (7/7 hand-verifiable sample passed) | 1.00 | under a minute | @Zhian_lagal_to (7–0) |
| @R4ash | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | @R4ash (3–2) |
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. None of the 10 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 19 October 2021 to 27 December 2021. 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 3 channels, the one whose matching posts we hold earliest is @Zhian_lagal_to. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual, 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 3 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 |
|---|---|---|
| 12 Aug 2026, 08:46 | 10 | no change |
| 6 Aug 2026, 23:32 | 10 | first reading |
20 posts held, back to 18 October 2021 — 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 20 posts for this entry, the most recent from 27 December 2021. An engagement rate over an empty window would be a number about nothing.
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. Below Telegram’s rounding threshold, so these counts are exact.
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.
مێلینا دوونیایەک لە جوانی نووسین
Signed لیستــVIP
باشترین چەناڵەکانی تێلیگرام لەم لیستەیا هەیە جۆینی هەموویان بە🕊🌍 ━━━━━━━༺𝗩𝗜𝗣༻━━━━━━━ ❥︎🌍🕊➺@Rabrdwm ڕابردووم ❥︎🌍🕊➺@boaww بۆئەو ❥︎🌍🕊➺@h4sti_kchek هەستی کچێک ❥︎🌍🕊➺@melin4m مێلینیا ❥︎🌍🕊➺@p2dza وێنە ❥︎🌍🕊➺@myyloove خۆشەویستم ❥︎🌍🕊➺@sh3r_captian شعر ❥︎🌍🕊➺@Rozhin_Work ڕۆژە ━━━━━━━༺ 9K༻━━━━━━━ ❥︎🌍🕊➺@boaww بۆ ئەو ❥︎🌍🕊➺@myangel20 فریشتەکەم ❥︎🌍🕊➺@Rabrdwm ڕابردوو ━━━━━━━༺ 4K༻━━━━━━━ ❥︎🌍🕊➺@qsay_kchik قسەی کچێک ━━━━━━━༺ 3K༻━━━━…
Signed لیستــVIP
𝑳𝒊𝒔𝒕 𝑺𝒉𝒂𝒓𝒌 𝑽𝒊𝒑 400𝐊 !💚 ➳l 🔥•• جوانترین چەناڵەکانی تێلێگرام ➳l 🔥•• Text - ViDiO - MuSiC •• ➳l 🔥 •• لەیەکەم تاکۆتایی جۆینیان بکەن 𝐒𝐀𝐑𝐎𝐊 𝐋𝐄𝐒𝐓𝐓 @Sharkmm 🤺! @BirTanem_0 گرووپـچات !❤️🔥 𝐉𝐨𝐢𝐧 𝐀𝐥𝐥 𝐂𝐡𝐚𝐧𝐧𝐞𝐥𝐬 𝐁𝐞𝐥𝐨𝐰𝐬 !🪐 💚•► @promesii : 47𝐊 💚•► @n4fr4t : 17𝐊 💚•► @BirTanem_0 5𝐊 ✦🩸5𝐊𝗦𝗨𝗕𝗦𝗖𝗥𝗜𝗕𝗘𝗥𝗦🩸✦ 🧡•► @photo_vid فـۆتۆ ڤیدۆ 🧡•► @INFINITY12323 ئیـنفنیتی 🧡•► @yadgaret یــادگاری 🧡•► @wenay_jwan ووێــنەی جوان 🧡•► @az1zzek ئـازیزێکـ 🧡•…
Signed 𝑳𝒊𝒔𝒕 𝑺𝒉𝒂𝒓𝒌 𝑽𝒊𝒑
﷽ 👨🏻💻لـیسـتـی ژمـارە یـەکی تـێلیگـرام پڕاو پڕ لە کەناڵی نایاب و گەورە🪐🖤! جوین ئێدیتۆرەکان😽🖤! { @B_EKA4S } جویـن خۆشتریـن گروپ چاتت😽💗! { @B_EKA4S } ┯─────•VIP•─────┯ 🪐🖤 @B_EKA4S ئێدیـتورلـد 🪐🖤 @Xami_Payiz خەمی پایز 🪐🖤 @galaxy_u_iphone گالاکسیو ئایفۆن 🪐🖤 @wrdil4kam وردیـلە 🪐🖤 @Qsakani_dlm قسەکانی دڵـم 🪐🖤 @B_EKA1S فۆتۆ 🪐🖤 @B_EKA2S ئەنگێـل 🪐🖤 @B_EKA3S ئەشقەکەمان 🪐🖤 @B_EKA4S ئێدیتورلـد …
Signed 𝟔𝟔𝟔⎮7𝐀𝐒𝐒𝐀 ✞🖤!'
https://t.me/kteb1
Signed 𝗦ᗩᖇOK 🤍☕️•℡
کەسی لێ ماوە بەم کاتە ناخەوتبێت؟💔
Signed DYA BOT LIST🌚🧡
جوانترین لیستی vip تلیگرام 400k نایاب ترین جەنالەکان لێرە ببینن هەموو جۆرە جەنالیک لامان بەردەستە💙 سەرەتا جۆینی جەنالەکانم بکەن😊◤◥ @XOSHAWEST_M @NAFASAKA_M @wrdil4kam @ASQKA_M @YARAKA_M @GRYANE_DLM @JWANY_yar @REGAY_rastt @haste_dlm1 @trpay_dlm @zamakanm ┣═══⚡ALKTRONE⚡═══┫ @M4ngy_Mn مانگی من @m4rdo سولتان @Graphic_photos ستۆری بێ لۆگۆ @dlishin دلی شین @Pennymar دابرانی ئیشق @boaww بۆ ئەو @qsay_kurek قسەی کورێک @ru7ak…
Signed SOZAN،🗞❤️!
هەموو پۆستە خۆشەویستیەکان لێردا ببینە تایبەت بە ئاشقان🌻 @NAFASAKA_M
Signed SOZAN،🗞❤️!
┏❥ ﷽ ┆ جوانترین کەناڵەڪانی تێلیگرام ➺✨🧸 🧸✨ ➺ تەنها چاوێکیان لێ بنێ و جۆین بە ➺ ➺ ســـہࢪەتــا ئـــہمـہ جــۆین بـڪـہ✨🧸 ┆ ┗┄┄┄┄┄┄┄┄┄┄┄┈┓ 【_____ @octooberr _____】 【_____ @dnawsarok _____】 【_____ @dnawsarok _____】 🧸✨لیستی چانێڵە کوردیەکان✨🧸 • • • • • • • • • • • • • • • • • • • • • • • • • • • VIP CHANAL ┄┄┅━𖤓🧸✨𖤓━┅┄ 🧸✨•➳@dnawsarok جاک…
Signed ﮼سەرۆک ﮼لیست ﮼3k
بەدوای جیدا دەگەری لای ئیمە دەسەکەوی💛
Signed SOZAN،🗞❤️!
لیستێکی تایبەت جوانترینەکانم هێناوە بۆتان (@dnawsarok ) (@octooberr ) (@dll_bar) +1k ━┅┅┄┄⊱✿⊰┄┄┉┉━ 🐻@dnawsarok دنـە و سـەرۆک 🐻@melin4m مێلینام 🍯@dnawsarok وتەی ئینگلیزی 🍯@dll_bar دڵـبـەر 🐻@GeRoDaTm گیرۆدەتم 🐻@Breni_dlik برینی دڵێک 🍯@ShEt0M شێتۆم 🍯@n4fasakam نەفەسەکەم 🐻@video_star_work فێدیۆ ستار 🐻@R4ash ڕەش 🍯@taqa_y4r تاقە یار 🍯@nayauet نایەوێت 🐻@zhian_babe_to ژیان بەبێ تۆ 🐻@droiyar درۆی یار 🍯@alvida_a ئەفێڵدا 🍯@DAR…
Signed ﮼سەرۆک ﮼لیست﮼١ک
سڵاو لە هەموو لایەک من بە ناوی سەرۆک داوای لێبوردن لە هەموو ئەو چەناڵانە بە ناوی منەور سفر کراوتوە بڕواتان هەبێت زیاد لە ٢٠ چەناڵی خۆشم سفر کراوەتەوە هیوادارم کەس دڵی پیس ناکات بەرامبەرم سوپاسی هەموو لایەک دەکەم ئەوەش یوسەری خۆم @sarrokm1
Signed qawaxanalist
Showing the 12 most recent of 20 posts we hold for @zhian_babe_to. 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.
@zhian_babe_to named 134 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
84 more handles are in this same list but not shown individually here — capped at 50.
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.
“ژیــان بەبێ تــۆ💔” (@zhian_babe_to), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/zhian_babe_to.
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.