Telegram RegisterThe public register of Telegram
Telegram profile photo for yazn_108

Channel

yazn_108

@yazn108

On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

485subscribers

+5 since we began measuring on 30 August 2026

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

Register entry

Telegram ID-1001436976448
TypeChannel
Username@yazn108
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 August 2026
Last confirmed live16 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/yazn108

Topic

Education — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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

480485482.530 August 2026 — 480 subscribers30 August 2026 — 480 subscribers30 August 2026 — 481 subscribers9 September 2026 — 483 subscribers16 September 2026 — 485 subscribers30 August 202616 September 2026
5 measurements spanning 17 days, net +5. 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 479–486 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 15:20485+2
9 Sept 2026, 06:18483+2
30 Aug 2026, 22:06481+1
30 Aug 2026, 06:45480no change
30 Aug 2026, 06:30480first reading

Engagement

20 posts held, back to 29 March 2025the 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 23 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

30 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 90.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2790.0%
👎13.33%
👏13.33%
🔥13.33%

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 19 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 30 reactions 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 29 March 2025 to 23 June 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

23 Jun 2026, 04:50 UTC207 viewsread 30 August 2026
Photo

بالصدفة اكتشفت MongoDB Atlas Search من مقطع المهندس Yahya ElAraby عن قواعد البيانات فكرته انك بدل ما تدير عملية الـsearch في موقعك بشكل شبه يدوي -في حال كنت تعتمد على MongoDB- اعطاك الحل على شكل محرك (Search Engine) كامل يدير عملية البحث من وإلى وبسرعة اعلى من مجرد ارسال استعلامات داخل قاعدة البيانات (اللي هي طريقتي سابقا في منصة المقالات مُركَّز) بالإضافة إلى البحث باستخدام جزء من كلمة او الكلمات المتشابهة وشوية ام

1 May 2026, 09:24 UTC397 views1 reactionsread 30 August 2026

اصبح كملف Notion بمناسبة ان اليوم جمعة قمت بتفريغ كُتَيِّب الصحيح والحسن من اذكار اليوم من كُتَيِّب الشيخ ابن باز رحمه الله "تحفة الأخيار ببيان جملة نافعة مما ورد في الكتاب والسنة من الأدعية والأذكار" إلى ملف نوشن المميز بالكُتَيِّب انه اورد فيه فقط صحيح وحسن الاسناد ولكن كحديث كامل فقمت بتفريغ الاذكار بشكل مجرد بحيث يسهل نسخها كلها او جزء منها وقراءته بشكل مباشر https://binbaz-tuhfat-al-akhyar.notion.site/3499d42

1

12 Apr 2026, 17:14 UTC451 views1 reactionsread 30 August 2026

خاصة بعد مشكلة تعطل بعض سيرفرات mongodb في الشرق الاوسط البعض مننا واجه اشكالية فقدان البيانات فاستعنت حاليا بـGitHub Actions لأنشاء سجل لمقالاتي في منصة مُركَّز بشكل تلقائي عند النشر او التعديل او الحذف هنا بامكانك اخذ فكرة عن كيف استفدت من GitHub Actions لانشاء سجل تلقائي للمقالات الريبو: https://github.com/yazn-108/murakkaz-articles-backup المنصة: murakkaz.vercel.app

1

12 Apr 2026, 17:14 UTC374 views0 reactionsread 30 August 2026

الـGitHub Actions من الأدوات الأساسية داخل GitHub وتُستخدم لأتمتة مهام التطوير مثل الـbuild والـdeploy وما شابه باستخدام شوية اوامر مكتوبة داخل ملفات YAML فهنا كورس مجمع على شكل فيديو واحد يشرح الية التعامل مع GitHub Actions بطريقة اجدها واضحة https://youtu.be/7gJFHjXscr8?si=RmQRtlb7-LRzcKWI

26 Mar 2026, 21:46 UTC353 views2 reactionsread 30 August 2026

طبعا هي ممكن تكون مع Nosql او مع SQL ولكن هو يشرح عن الـinjection في Nosql

1👏1

26 Mar 2026, 21:44 UTC341 views2 reactionsread 30 August 2026

لاحظت قلة التفات لموضوع Nosql injection رغم انه مؤذي جدا لو احد استغله مع قاعدة بياناتك هنا شرح بالعربي + معاه ملف notion https://youtu.be/Zach0wsFrlE?si=RWYfWaKDqiZb1Ye1 ملف الـnotion https://perpetual-glue-afd.notion.site/Nosql-injection-3089f26cb516805699f2fef63c768133 هو يشرح عنها نفسها وليس عن طرق الحماية من استغلالها ولكن تعلمك عنها يساعدك تصير تفكر كيف تحط شروط للمدخلات وتنظيفها قبل ارسالها لقاعدة البيانات

2

24 Mar 2026, 15:17 UTC325 views1 reactionsread 30 August 2026

تطبيق عربي اعجبت فيه جدا يجمع مابين فكرة slack و teams و zoom وبنفس الوقت منتج سعودي حتى السيرفرات داخل السعودية يعني تخضع لموضوع القوانين السعودية في حماية البيانات ويدعم الاستخدام من مختلف الدول https://beem.sa/ ليس اعلان وانما اعجاب في مدى توافق التطبيق مع تفضيلاتنا كعرب

1

19 Mar 2026, 15:31 UTC319 views1 reactionsread 30 August 2026

كل عام وانتم بخير، عيد مبارك نتذكر قول الله "ذَٰلِكَ وَمَن يُعَظِّمْ شَعَائِرَ اللَّهِ فَإِنَّهَا مِن تَقْوَى الْقُلُوبِ" فالفرح واظهار السعادة من تعظيم شعيرة الله فافرح ولا داعي لتذكر غير الافراح فيه مهما كان حالك او وضعك

1

18 Jan 2026, 19:40 UTC465 views1 reactionsread 30 August 2026

وايضا عبر لينكيدإن https://www.linkedin.com/in/yazn-ahmed

🔥1

18 Jan 2026, 19:39 UTC446 views1 reactionsread 30 August 2026

قد يكون قل تركيزي عن النشر في القناة هنا لأن اغلب المعلومات اصبحت انشرها عبر منصة مُركَّز ونشرتها البريدية https://murakkaz.vercel.app/

1

1 Nov 2025, 13:40 UTC613 views2 reactionsread 30 August 2026

كورس جميل جدا في React Design Patterns https://youtu.be/B09-J84p0ck?si=aCoCH1hxN2VQzrE1 وهنا قمت بتلخيص الفيديو بمقالة بسيطة ولكن لا تغني عن مشاهدة الفيديو https://murakkaz.vercel.app/article/react-design-patterns وهنا قمت بتطبيق هذه الباترنس على موقعي (منصة مُركَّز) https://github.com/yazn-108/articles-nextjs

2

27 Sept 2025, 19:12 UTC546 views2 reactionsread 30 August 2026

حماية الـarray في JavaScript https://murakkaz.vercel.app/article/safe-array-methods/

2

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

الحور للعلوم كتب الثانوية ٢٠٢٧
@DrHananMohamed · 24,566
Telegram ranks this channel #16 of 49 here — alongside 48 others — read 16 September 2026
برمجة وتطوير
@pro2dev · 40,511
Telegram ranks this channel #26 of 64 here — alongside 63 others — read 30 August 2026
منصة سطر
@tuwaiq_codes1 · 30,715
Telegram ranks this channel #41 of 62 here — alongside 61 others — read 6 September 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“yazn_108” (@yazn108), 485 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/yazn108.

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.