Telegram RegisterThe public register of Telegram
Telegram profile photo for الـيَـاسِـيـن

Channel

الـيَـاسِـيـن

@Gazayasin

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

9,390subscribers

-354 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001778573216
TypeChannel
Username@Gazayasin
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/Gazayasin

Topic

Religion — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Growth

9,3909,7449,5677 August 2026 — 9,744 subscribers7 August 2026 — 9,744 subscribers10 August 2026 — 9,718 subscribers13 August 2026 — 9,693 subscribers16 August 2026 — 9,667 subscribers20 August 2026 — 9,633 subscribers23 August 2026 — 9,597 subscribers26 August 2026 — 9,573 subscribers30 August 2026 — 9,546 subscribers2 September 2026 — 9,504 subscribers7 September 2026 — 9,454 subscribers11 September 2026 — 9,416 subscribers15 September 2026 — 9,390 subscribers7 August 202615 September 2026
13 measurements spanning 39 days, net -354. 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 9,337–9,797 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 10:009,390-26
11 Sept 2026, 18:209,416-38
7 Sept 2026, 10:009,454-50
2 Sept 2026, 17:479,504-42
30 Aug 2026, 08:449,546-27
26 Aug 2026, 22:029,573-24
23 Aug 2026, 23:149,597-36
20 Aug 2026, 02:589,633-34
16 Aug 2026, 20:469,667-26
13 Aug 2026, 08:159,693-25
10 Aug 2026, 17:519,718-26
7 Aug 2026, 14:459,744no change
7 Aug 2026, 14:349,744first reading

Engagement

71 posts held, back to 2 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 34 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.72%
avg views ÷ 9,390 subscribers
Avg views / post
537
14 posts measured
Reaction rate
3.56%
reactions ÷ views · ER floor
Posts in window
14
of 71 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 28 August 2026
Posts held71 (2 August 202628 August 2026)
Views total7,524
Reactions total268
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 05:54 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.

What this channel posts

Video runtime
29m 16s
Average length
1m 50s

Measured directly from 16 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.

Reaction mix

1,501 reactions across 71 posts, in 12 distinct kinds. The most used accounts for 81.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,22581.6%
🫡1087.20%
💔704.66%
💯332.20%
👍161.07%
🕊130.866%
😢130.866%
😍120.799%
👌40.266%
30.2%
🔥20.133%
🥰20.133%

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

Measured over the 71 most recent posts we hold, published 2 August 2026 to 28 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

28 Aug 2026, 06:48 UTC269 views22 reactionsread 29 August 2026

اللهُمَّ صَلِّ وسَلِّم على نَبِيِّكَ نَبِيِّ المَلحَمَة، حَامِلِ السَّيفِ بِالحَقِّ، ورَافِعِ رَايَةِ النَّصرِ، الَّذِي هَزَمتَ بِهِ جُمُوعَ الكُفرِ، وزَلزَلتَ بِهِ عُرُوشَ الطُّغَاةِ. اللهُمَّ صَلِّ على مَن أَرْسَلتَهُ قَائِدًا لِلغُزَاة، ومُلهِمًا لِلمُجَاهِدِينَ، يَنصُرُ دِينَكَ ويُقِيمُ العَدلَ فِي الأَرضِ، حَتَّى دَانَتْ لَهُ الأُمَمُ، وخَضَعَتْ لَهُ الرِّقَاب؛وصَلِّ على آلِهِ الأَطهَار، وصَحبِهِ الأَبرَارِ، سُي

18🫡2😍2

27 Aug 2026, 20:42 UTC380 views23 reactionsread 29 August 2026
Video

يا حبَّذا الجنَّة، وحِلوُ رِياضها فكلُّ ما هُنا مُتعِب، وكلُّ من هنا مُتعَب

23

26 Aug 2026, 22:34 UTC492 views21 reactionsread 29 August 2026

- قَّد ينالُ المُؤمنُ بدعاءِ أخيهِ مالا يُدركُهُ بدعائِه لنفسِه ) فلا تغفلوا عنا 💔

21

26 Aug 2026, 17:10 UTC542 views23 reactionsread 29 August 2026
Photo

اللهمَّ اجعل رايتَنا عزًّا بالإيمان، ونورًا بالقرآن.

21💯2

26 Aug 2026, 14:20 UTC554 views22 reactionsread 29 August 2026
Photo

يا رب أطلِق بالقُرآن لِساني وثبِّت بِه جنانِي، وسدِّد بِه مآربي.. واجعلهُ شفيعي يوم ألقاك....

19💯3

26 Aug 2026, 09:20 UTC512 views14 reactionsread 29 August 2026
Video

وأن ما فاتك في الدنيا ستلقاه في الجنة🥹 اللهم عفوك وعافيتك وسترك ورضاك والفردوس الأعلى من الجنة بلا حساب ولا سابقة عذاب سبحوا الملك القدوس 🥀 وصلوا على خير الورى محمد ﷺ

11😍2💯1

26 Aug 2026, 09:19 UTC475 views14 reactionsread 29 August 2026

‏﴿ وَذَكِّرْ فَإِنَّ الذِّكْرَىٰ تَنفَعُ الْمُؤْمِنِينَ ﴾ ‏- سُبحان الله . ‏- الحَمد لله . ‏- لا إله إلا الله . ‏- الله أكبر . ‏- لا حَول و لا قوة إلا بالله . ‏- سُبحان الله و بِحمده . ‏- سُبحان الله العَظيم . ‏- أستغفِرُ الله الْعَلِيُّ الْعَظِيم وَأَتُوبُ إِلَيْهِ. -لا إِلَهَ إِلا أَنتَ سُبْحَانَكَ إِنِّي كُنتُ مِنَ الظَّالِمِينَ. -اللَّهُمَّ صَلِّ وَسَلِّمْ عَلَى نَبِيِّنَا مُحَمَّدٍ. -يا مقلِّبَ القلوبِ ثَبِّتْ ق

14

25 Aug 2026, 19:15 UTC570 views22 reactionsread 29 August 2026
Video

🔴"غزة شعار، قصف ودمار".. جنود من الجيش السوري يهتفون لغزة داخل قلعة دمشق، خلال عرض عسكري. طوفان التحرير قادم ⏳🔥

22

25 Aug 2026, 09:34 UTC636 views24 reactionsread 29 August 2026
Photo

• غَدًا نَلْقَى الأَحِبَّةَ، مُحَمَّدًا وَصَحْبَهُ... قَالَهَا بِلال رَضِيَ اللهُ عَنْهُ عِنْدَ احْتِضَارِهِ، رَدًّا عَلَى زَوْجَتِهِ حِينَ قَالَتْ: «وَاحَزَنَاهُ!»، فَقَالَ: "بَلْ "وَافَرَحَاهُ" غَدًا نَلْقَى الأَحِبَّةَ ، مُحَمَّدًا وَصَحْبَهُ!

24

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

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

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.

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

“الـيَـاسِـيـن” (@Gazayasin), 9,390 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/Gazayasin.

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.