Telegram RegisterThe public register of Telegram
Telegram profile photo for مێژوو

Channel

مێژوو

@Dirok_2727

On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry

98subscribers

-4 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1004290622362
TypeChannel
Username@Dirok_2727
CreatedBetween 1 May 2026 and 1 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live17 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/Dirok_2727

Growth

981021009 August 2026 — 102 subscribers9 August 2026 — 102 subscribers9 August 2026 — 101 subscribers17 August 2026 — 98 subscribers9 August 202617 August 2026
4 measurements spanning 8 days, net -4. 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 97–103 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 11:2398-3
9 Aug 2026, 17:01101-1
9 Aug 2026, 10:01102no change
9 Aug 2026, 03:48102first reading

Engagement

20 posts held, back to 1 July 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 20 posts for this entry, the most recent from 10 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

31 reactions across 13 posts, in 3 distinct kinds. The most used accounts for 83.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2683.9%
💔39.68%
🕊26.45%

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

Measured over the 20 most recent posts we hold, published 1 July 2026 to 10 July 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

10 Jul 2026, 14:58 UTC140 views0 reactionsread 9 August 2026
Poll

بەس ژیاننامەی کەسە گەورەکان دابنێنن؟

  1. بەڵێ دڵخۆش دەبین44%
  2. نە با چالاکی تریش بێت53%
  3. نە دایانمەنێ3%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

9 Jul 2026, 12:44 UTC142 viewsread 9 August 2026
Forwarded from @peshaWaqaZimuhammadFile

@peshaWaqaZimuhammad #چنگیز_سیگارچی:پووشپەڕ هەر لەڕێدایە گەلە بێ نازەکەت . . . @peshaWaqaZimuhammad

8 Jul 2026, 12:05 UTC123 viewsread 9 August 2026

فاتە ڕەش شاژنە یاخییەکەی کوردستان فەرماندەی ٤٠٠٠چەکدار و پاڵەونی جەنگی کرایم ئەو ژنەی سوڵتانی عوسمانیی ناچار بە بێدەنگی کرد چۆن مێژووی فاتە ڕەش کرا؟ بە قوربانیی پڕۆژەی تورکاندن؟

8 Jul 2026, 12:05 UTC91 views0 reactionsread 9 August 2026
Photo

ئەو ژنە ئازایە کێیە و دەیناسن؟

6 Jul 2026, 17:30 UTC114 views3 reactionsread 9 August 2026
Photo

شاهیدن ئەوانەی بۆ پارچە نانێک و بۆ مانەوە لە ژیان، ڕێگەی سەخت و بەفراوی چیایان گرتووەتە بەر، هەموو کات لە دڵی خەڵکدا ئەژین بەڵام ئێوە؟ ئێوە لە بیرەوەریی ئەم نیشتمانەدا، تەنیا وەک پەڵەیەکی ڕەش، وەک نیشانەیەک بۆ زوڵم و بێ باکیی مرۆڤ بەرامبەر مرۆڤ ئەمێننەوە خوێنی کۆڵبەرێک، ئاو نییە بە زەویدا بچێت. ئەو خوێنە، ئەبێتە هاوارێک کە چیاکانیش ئەیبیسن.

💔3

6 Jul 2026, 10:48 UTC121 views1 reactionsread 9 August 2026
Photo

خووشکە شیرینەکەم هەرچەند بچووکی بەڵام دڵت گەورەیە تۆ تەنها منداڵێک نیت تۆ هیوای سبەی کوردستانیت. با هەمیشە سەربەرز بیت بە کوردبوونت و خۆشەویستی نیشتمانت چونکە کوردایەتی بە دڵ دەژی نەک بە تەمەن و تۆ گولێکی جوانی باخی نیشتمانت https://t.me/Dirok_2727

1

5 Jul 2026, 20:59 UTC106 views1 reactionsread 9 August 2026
Forwarded from @Kurd_hilak_i1

کتێبی قاسملوو و هەژار عەقڵت پڕ دەکەن، هێمن و شێرکۆش دڵت:))

🕊1

5 Jul 2026, 20:44 UTC101 views2 reactionsread 9 August 2026
File

ئاڵای من هەر ڕەنگینه ئامانجم ئازادییه نازانم مردن چییه کوردم من ئاگرم یان کوردستان یان مردن🔥

2

5 Jul 2026, 06:23 UTC192 views1 reactionsread 9 August 2026

فاتە ڕەش شاژنە یاخییەکەی کوردستان فەرماندەی ٤٠٠٠چەکدار و پاڵەونی جەنگی کرایم ئەو ژنەی سوڵتانی عوسمانیی ناچار بە بێدەنگی کرد چۆن مێژووی فاتە ڕەش کرا؟ بە قوربانیی پڕۆژەی تورکاندن؟

1

5 Jul 2026, 05:37 UTC172 views2 reactionsread 9 August 2026
Photo

ئەو ژنە ئازایە کێیە و دەیناسن؟

2

3 Jul 2026, 19:59 UTC139 views1 reactionsread 9 August 2026

ئازادی تەنها وشەیەک نییە گیانی گەلێکە کە هەرگیز بۆ کڕین نەفرۆشراوە

1

3 Jul 2026, 13:51 UTC126 views3 reactionsread 9 August 2026
Forwarded from @Barziar

خۆت بپارێزە لــە ئاهی دڵ بریندارانـی شەو نەک خودا ناکەردە گیرا بێ، دوعای ناڵانی شەو — شێخ نووری شێخ ساڵـح

3

Showing the 12 most recent of 20 posts we hold for @Dirok_2727. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

10 Jul 2026, 14:58 UTCAnonymous Poll32 voters

بەس ژیاننامەی کەسە گەورەکان دابنێنن؟

  1. بەڵێ دڵخۆش دەبین44%
  2. نە با چالاکی تریش بێت53%
  3. نە دایانمەنێ3%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 1 July 2026 to 10 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 733,416 of 1,548,671entries 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.

Mentions

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.

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 17 August 2026 — this entry's latest reading, not the date you are reading this.

“مێژوو” (@Dirok_2727), 98 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/Dirok_2727.

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.