Channel
@MGLNaJ
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
16,063subscribers
+191 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001618538285 |
|---|---|
| Type | Channel |
| Username | @MGLNaJ |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 47 |
| Confirmed unchanged | 1 time, most recently 24 October 2026 |
| On Telegram | t.me/MGLNaJ |
Job listings — 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 10 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Oct 2026, 15:00 | 16,063 | -8 |
| 23 Oct 2026, 14:48 | 16,071 | -9 |
| 22 Oct 2026, 16:31 | 16,080 | -13 |
| 21 Oct 2026, 10:59 | 16,093 | -5 |
| 20 Oct 2026, 11:38 | 16,098 | -6 |
| 19 Oct 2026, 09:15 | 16,104 | +3 |
| 18 Oct 2026, 12:48 | 16,101 | -4 |
| 17 Oct 2026, 12:16 | 16,105 | -7 |
| 16 Oct 2026, 11:30 | 16,112 | +5 |
| 15 Oct 2026, 12:01 | 16,107 | -1 |
| 14 Oct 2026, 10:00 | 16,108 | +7 |
| 12 Oct 2026, 22:29 | 16,101 | -5 |
| 8 Oct 2026, 08:36 | 16,106 | +6 |
| 3 Oct 2026, 21:15 | 16,100 | -2 |
| 25 Sept 2026, 04:57 | 16,102 | +87 |
| 18 Sept 2026, 21:58 | 16,015 | -2 |
| 16 Sept 2026, 13:01 | 16,017 | +14 |
| 14 Sept 2026, 17:38 | 16,003 | +2 |
| 13 Sept 2026, 06:19 | 16,001 | +17 |
| 11 Sept 2026, 09:37 | 15,984 | first reading |
123 posts held, back to 1 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 54 pages 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 123 posts for this entry, the most recent from 1 September 2026. An engagement rate over an empty window would be a number about nothing.
241 reactions across 60 posts, in 6 distinct kinds. The most used accounts for 42.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 102 | 42.3% | |
| ❤ | 87 | 36.1% | |
| 🤣 | 47 | 19.5% | |
| 👍 | 3 | 1.24% | |
| ❤🔥 | 1 | 0.415% | |
| 🔥 | 1 | 0.415% |
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 75 of the 123 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 241 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 123 most recent posts we hold, published 1 August 2026 to 1 September 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.
الشركة: قباني وكنيفاتي •المسمى الوظيفي: مراسلات •قسم: المراسلات (المنطقة الحرة) ⚫المهارات والمؤهلات المطلوبة: - اختصاص إدارة أعمال أو محاسبة أو أدب إنكليزي - اللغة الإنكليزية جيدة - خبرة لا تقل عن سنتين في المراسلات التجارية - العمر بين 22 إلى 35 سنة - ساعات العمل من الساعة 8:30 صباحا إلى الساعة 5:00 مساء - العطلة الأسبوعية يوم الجمعة •للتقديم يرجى إرسال البيانات الشخصية عبر الواتساب مع ذكر الشاغر الوظيفي على الرق…
👎4
فرصة عمل Customer Service Team Leader تعلن BeinMedia عن توفر شاغر Customer Service Team Leader للانضمام إلى فريقها في مقر الشركة بدمشق. 🎯 المسؤوليات والمهام قيادة وإدارة فريق الـ Customer Service وتدريب أعضائه وتطوير مهاراتهم. تنظيم وتوزيع الشيفتات بما يضمن استمرارية وتغطية العمل. وضع ومتابعة KPIs وقياس أداء الفريق وإعداد تقارير الأداء. متابعة جودة التعامل مع الاتصالات والرسائل الواردة والتأكد من الالتزام بمعايير خدم…
#Job_Opportunity #Angular_Developer #FrontEnd_Developer #Full_Time #Remote Softqu Innovation Hub is looking to hire a Front-End Developer with strong Angular experience. Responsibilities 1- Design & develop responsive web pages for mobile and desktop. 2- Develop & maintain web applications using TypeScript, Angular and Tailwind. 3- Collaborate with designers and backend developers to deliver high-quality features. 4-…
Remote · Syria | Part-Time Contract | Frontend Developer| Aleppo Preferred Dahhan Enterprises is looking for a senior design-first professional with strong capabilities across brand identity, UI/UX, visual design, and frontend implementation. You should be comfortable taking work from concept to production—moving between creative direction, Figma, and code. Hands-on frontend implementation is required, using: Next.js…
❤2
#JobOpportunity #Backend_Developer #Backend #ASP_Net_Core #ASP_API #C_Sharp #Net_Core #EF_Core #Full_Time #Remote Softqu Innovation Hub is looking to hire a ASP.Net Backend developer. Responsibilities 1- Develop and maintain API services using C#, .NET 8 or newer, and ASP.NET. 2- Develop and maintain advanced, cacheable queries using EF Core, SQL Server, and Redis. Requirements 1- Diploma or higher in Information Tec…
Frontend Developer Wege is hiring a: Frontend Developer – Next.js Requirements: Strong experience with Next.js Advanced experience with React Strong hands-on experience with React Native Experience building fast, responsive, and scalable user interfaces Good understanding of API integrations and backend connectivity Experience in performance optimization and UX is a plus To apply, please send: CV / Resume Portfolio o…
👎4
Backend Developer Wege is hiring a: Backend Developer – Python / Django Requirements: Strong experience with Python Advanced experience with Django and Django REST Framework Experience designing and developing REST APIs Good database experience, preferably PostgreSQL Strong experience with AI and LLM integrations Hands-on experience integrating AI models into real production backend systems Experience with scalable a…
الشاغر الوظيفي: Video Editor الناشر: Valencia متطلبات الفرصة: 1_ خبرة مثبتة في مجال تحرير الفيديو مع سجل أعمال مميز. 2_ إتقان برامج التحرير مثل Adobe Premiere Pro و After Effects. 🔹قدم الآن على الشاغر من هنا! واطلع على تفاصيل أكثر حول الفرصة. 🔹حمل تطبيق فرصة للتوظيف الآن: App Store|Direct Link|Google Play
الشاغر الوظيفي: مدير تسويق - Marketing Manager الناشر: شركة خاصة متطلبات الفرصة: 1_ بكالوريوس في التسويق، إدارة الأعمال، الإعلام، التجارة أو اختصاص ذي صلة. 2_ خبرة عملية تقريبًا من 3 إلى 5 سنوات في مجال التسويق. 🔹قدم الآن على الشاغر من هنا! واطلع على تفاصيل أكثر حول الفرصة. 🔹حمل تطبيق فرصة للتوظيف الآن: App Store|Direct Link|Google Play
❤1
الشاغر الوظيفي: Full Stack ( Mid - Senior ) الناشر: شركة خاصة متطلبات الفرصة: 1_ بكالوريوس في علوم الحاسوب أو مجال ذي صلة. 2_ خبرة لا تقل عن 3 سنوات في البرمجة. 🔹قدم الآن على الشاغر من هنا! واطلع على تفاصيل أكثر حول الفرصة. 🔹حمل تطبيق فرصة للتوظيف الآن: App Store|Direct Link|Google Play
🤣19
الشاغر الوظيفي: مصمم/ة جرافيك الناشر: Movo Delivery متطلبات الفرصة: 1_ خبرة و إتقان برامج التصميم مثل Photoshop, Illustrator, InDesign 2_معرفة في منصات التواصل الاجتماعي. 🔹قدم الآن على الشاغر من هنا! واطلع على تفاصيل أكثر حول الفرصة. 🔹حمل تطبيق فرصة للتوظيف الآن: App Store|Direct Link|Google Play
الشاغر الوظيفي: Architectural Designer الناشر: شركة خاصة متطلبات الفرصة: 1_ تطوير مفاهيم تصميمية إبداعية للأثاث والمنتجات بناءً على متطلبات المشروع. 2_ إعداد الرسومات الفنية والتخطيطات ومواصفات التصميم التفصيلية. 🔹قدم الآن على الشاغر من هنا! واطلع على تفاصيل أكثر حول الفرصة. 🔹حمل تطبيق فرصة للتوظيف الآن: App Store|Direct Link|Google Play
Showing the 12 most recent of 123 posts we hold for @MGLNaJ. 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.
@MGLNaJ edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
This channel appears in 22 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 24 October 2026 — this entry's latest reading, not the date you are reading this.
“Mohammad Najjar || محمد نجار” (@MGLNaJ), 16,063 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/MGLNaJ.
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.