Telegram RegisterThe public register of Telegram
Telegram profile photo for خەرمانی خەیاڵ

Channel

خەرمانی خەیاڵ

@sasanmonfared

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

316subscribers

+25 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1004407303977
TypeChannel
Username@sasanmonfared
CreatedBetween 1 June 2026 and 5 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/sasanmonfared

Growth

291316303.56 August 2026 — 291 subscribers6 August 2026 — 291 subscribers7 August 2026 — 293 subscribers15 August 2026 — 316 subscribers6 August 202615 August 2026
4 measurements spanning 8 days, net +25. 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 287–320 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 01:18316+23
7 Aug 2026, 01:34293+2
6 Aug 2026, 22:48291no change
6 Aug 2026, 16:16291first reading

Engagement

20 posts held, back to 5 August 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.

ERR · 30 days
27.7%
avg views ÷ 316 subscribers
Avg views / post
87.6
20 posts measured
Reaction rate
5.82%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (5 August 20266 August 2026)
Views total1,752
Reactions total102
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 22:48 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.

Reaction mix

102 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 54.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5654.9%
👏1817.6%
👍1615.7%
🔥65.88%
😁43.92%
🍓10.98%
🥰10.98%

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 20 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 102reactions 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 5 August 2026 to 6 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.

Recent posts

6 Aug 2026, 15:41 UTC62 views4 reactionsread 6 August 2026

سەرم بەرزتر دەبێ گەر بەرز ببیسم ناوی سەوڵاوا

3👏1

6 Aug 2026, 15:39 UTC62 views3 reactionsread 6 August 2026
File

دڵم+ناوێ+ئەگەر+تاوێ+نەبینم+چاوی+سەوڵاوا (1).MP3 شێعر:ساسان مۆنفەرێد[بێوەر] ناوی شێعر:سەوڵاوا

2👏1

6 Aug 2026, 15:33 UTC63 views3 reactionsread 6 August 2026

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

👍2👏1

6 Aug 2026, 09:18 UTC264 views8 reactionsread 6 August 2026

دروێ مەڎەو ئەگەر واچوو : جە قووڵایی دڵیمۆ وەشم مسیەی.. تۆ تا ئیسە 'سیروان"ت دیەن هاژە هاژوو تافەی کەفاویێش دروێ بۆ؟ "بۆژانە' و "هەزبە" کێفیلی "کۆساڵان"ی کەی بە دروێ ڕەنگ و بۆ وێشا مڎا جبەر؟ تا ئیسە جە دەنگوو شمشاڵەو شوانێوە دەربەدەریوە بە دروێ سۆزێوە ئامان جبەر ؟ نا .. ئازیزم... من دیوانە شێعرەو 'مەولەوی' و "بێسارانی" نا "سیاوچەمانە"ێوە ڕووت و پەتینا.. من شەماڵوو پێچەپێچەکاو ڕاو "هەزارانی' نا ئەگەر واچوو

6👏2

6 Aug 2026, 08:44 UTC70 views3 reactionsread 6 August 2026

نامەردە ئەوەی دەستی بە خوێناو ژنێ ئاڵە...

3

6 Aug 2026, 08:41 UTC73 views2 reactionsread 6 August 2026

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

👍2

5 Aug 2026, 19:32 UTC81 views2 reactionsread 6 August 2026

شێعری ژمارە 45 دەمی ژیری دەسکرد خۆش...

🥰1😁1

5 Aug 2026, 19:30 UTC82 views6 reactionsread 6 August 2026
File

کەتۆ+نیت+باخی+دڵ،+سووتاوە+ئازیز.MP3

5🔥1

5 Aug 2026, 19:18 UTC84 views3 reactionsread 6 August 2026

وەرە، با مەرگ نەکێشێ دەستی گیانم...

3

5 Aug 2026, 19:18 UTC84 views5 reactionsread 6 August 2026

45: کەتۆ نیت باخی دڵ، سووتاوە ئازیز هەناوم جێی خەم و زووخاوە ئازیز هەواری کۆنی پڕعەشقت، چ چۆڵە بەجارێ کەپری دڵ ڕووخاوە ئازیز هەناسەم بۆنی بێ تۆیی ئەکێشێ لە دووریت گۆمی چاو خوێناوە ئازیز بەیادی پێکەنینی پڕ لە سۆزت مەلی شەوقم لە ژین خنکاوە ئازیز خەیاڵی تۆ بەجێ ناهێڵێ هەستم گڕێ تیژت لە ناخ بەرداوە ئازیز نەماوە تاقەتی بێتاقەتی لام دڵم بۆ دیتنەوت لێداوە ئازیز بەکۆچت هێندە دڵتەنگم کە مردن بەجێگەی تۆ، لە ڕێم وستاوە ئا

4👍1

5 Aug 2026, 17:45 UTC72 views4 reactionsread 6 August 2026

شاسواری شاکچی بڕنەو لە شان یادی بەخێر...

4

5 Aug 2026, 17:41 UTC75 views7 reactionsread 6 August 2026

44: "ڕاز "و چیرۆکی شەوانەی لادێیەکان یادی بەخێر بۆنی "سمڵ" و "مێخەک"ی دایک نیشتمان یادی بەخێر کاگڵی دیواری حەوشە و باڕەباڕ کاژیلەکان نانەساجی و چەند "پشی" بان "نانە شان" یادی بەخێر بێسواخە؛ ژێری "داڵان" و ڕماوە کەپری ژین چاوێ پڕ لە شەرم و ماچی جێژوان یادی بەخێر دەوری "قورسین" ، پێکەنینی پاڵی سۆبەی پڕ لە دار "پاپالنجێ" چەند مناڵ لە دیوەخان یادی بەخێر کانیەکان وشک و چ چۆڵە بەردەنوێژی هانەکان دار هەوار زەردە و ماڵا

6👏1

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

Citation-graph rank — 263,651 of 1,481,217entries 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.

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.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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

“خەرمانی خەیاڵ” (@sasanmonfared), 316 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/sasanmonfared.

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.