Channel
@asseraaalsham1
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
45,174subscribers
+2,688 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001125348779 |
|---|---|
| Type | Channel |
| Username | @asseraaalsham1 |
| Description | فأما الزبد فيذهب جفاءً وأما ما ينفع الناس فيمكث في الأرض |
| Created | 9 September 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 October 2026 |
| Measurements held | 48 |
| Confirmed unchanged | 1 time, most recently 25 October 2026 |
| On Telegram | t.me/asseraaalsham1 |
Politics & activism — a classification, not a measurement. 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 |
|---|---|---|
| 25 Oct 2026, 15:06 | 45,174 | +35 |
| 24 Oct 2026, 12:59 | 45,139 | +39 |
| 23 Oct 2026, 15:36 | 45,100 | +38 |
| 22 Oct 2026, 17:47 | 45,062 | +30 |
| 21 Oct 2026, 13:05 | 45,032 | +4 |
| 20 Oct 2026, 13:05 | 45,028 | +36 |
| 19 Oct 2026, 13:11 | 44,992 | +50 |
| 18 Oct 2026, 09:36 | 44,942 | +70 |
| 17 Oct 2026, 11:37 | 44,872 | +53 |
| 16 Oct 2026, 09:01 | 44,819 | +57 |
| 15 Oct 2026, 05:47 | 44,762 | +39 |
| 14 Oct 2026, 02:29 | 44,723 | +25 |
| 11 Oct 2026, 15:16 | 44,698 | +174 |
| 7 Oct 2026, 06:00 | 44,524 | +119 |
| 2 Oct 2026, 07:58 | 44,405 | +306 |
| 18 Sept 2026, 11:40 | 44,099 | +85 |
| 16 Sept 2026, 03:21 | 44,014 | +152 |
| 14 Sept 2026, 06:59 | 43,862 | +199 |
| 12 Sept 2026, 17:40 | 43,663 | +94 |
| 10 Sept 2026, 18:42 | 43,569 | first reading |
317 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 157 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 25 October 2026 |
|---|---|
| Posts held | 317 (1 August 2026 – 25 October 2026) |
| Views total | 1,719,170 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 26 Oct 2026, 03:43 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.
Lifetime counters from Telegram’s own channel header, read 26 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 75 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.
#تجهيز_قوائم_اليمن - اسرائيل أنهت المرحلة الثانية من القضم المنظم للجنوب وستبدأ بفتح ممر إنساني من بلدة الحضر في القنيطرة إلى السويداء ، وهكذا تعزل درعا شمال الممر للسلطة وجنوب الممرّ لها. - أمريكا تستعد لتوجيه ضربة قاصمة لإيران لدفعها للانتقام والقيام بعمل بري ضد دول الخليج وسوريا والأردن ، يعني دير الزور تحت خطر الاجتياح ودمشق تحت خطر صواريخ إيران. - هذه جزء من المخاطر القادمة ووسط كل هذا أمر الشرع قادة الفي…
#فضيحة_رنكوس - لم يمض بضعة أشهر على فضيحة حادثة خان أرنبة عندما طبلت وزمرت السلطة على اعتقال خلية لداعش ثم تبين كذبة وافتراء التهمة حتى اضطرت وزارة الداخلية لتصدر بيان اعتذار بعد أن شهّرت بالمعتقلين وألبستهم المخطط حتى تكررت فضيحة رنكوس منذ يومين. - الشباب ليس لهم أس علاقة بداعش ومعظمهم من الفرقة ٤٤ وكانوا قبل التحرير أحرار شام ومع فراس بيطار وجيش إسلام ، فقط سمتهم ملتزمين دينياً عن حق وحقيق ولم يبيعوا دينهم ول…
Photo, posted without a caption
#جبل_الزاوية - وفاة ثلاث أطفال من بلدة واحدة في جبل الزاوية اسمها ( مرعيان) بلدغة أفعى أو عقرب ، لعدم وحود سيارات إسعاف كافية تنقلهم لأقرب مشفى ولعدم وحود مشفى في الجبل والمراكز الصحية ليس فيها مصل مضاد لسم العقارب والأفاعي. - عدد سكان جبل الزاوية ٤٠٠ ألف ومعروف أنه أكثر منطقة في سوريا ضحت وقدمت شهداء وقصف يعادل القنابل التي رميت على برلين في الحرب العالمية الثانية. - كل قرية فيها أقل شيء ٣٠٠ شهيد وكفر رومة في…
#ماكو_أوامر - انتشر فيديو لعنصر من السلطة في القنيطرة يصور مروحية اسرائيلية تحلق على علوّ منخفض ويقول لو فقط يعطونا أوامر كنّا أسقطناها. - هناك أوامر مشددة من الشرع بعدم الاقتراب والتماس والاحتكاك مع أي قوة اسرائيلية وقال لهم بالحرف مهما فعلوا قتلوا اعتقلوا داهموا جرفوا حرقوا لا تقتربوا منهم ( ماذا تريد اسرائيل أكثر من هكذا تسهيل لخطتها القضم المنظم وهذه مهمة الشرع) - أمريكا وتحديداً هذه المرة وكالة المخابرات …
Photo, posted without a caption
#تعز_الشموخ_مقبرة_الحوثي -كل من يفرق بين حصار اسرائيل لغزة وحصار الحوثي لتعز هو منافق وقولاً واحداً هو من مذهب التشيع السياسي الذي تحدث عنه الشيخ الددو الشنقيطي حفظه الله - لا يوجد شيء في الشريعة ولا السياسة تقول بدعم جهة لأنها تناصرني مقابل الصمت عن جرائمها في حق جهة أخرى . - الحوثي اجتمع مع الأمريكان وقال لهم لن نستهدف سفنكم ولا سفن الغرب ، سنستهدف فقط سفن السعودية فأين العداء مع أمريكا ؟ - الحوثي نفسه لم ينا…
سمعت أن هذا الغدار دلامة العلي يكذبني أقلع عيونك قلع إن كان ما قلته غير صحيح حتى رقم الغرفة بالفورسيزونس التي كان يقطنها موسى رقمها ١٢٢٤ هل تريد منّي أن أكتب ماذا فعلت بك دورية أمن القصر التي داهمت بيتك واستردت مبلغ المليون منك ؟ انضب واذهب تب إلى ربك من السرقات والعمولات والغدر وهذا أكبر من السرقات تندس في حراك إدلب الذي اندلع ضد بطش الهيئة ثم تقوم بتصوير وتسجيل كل كلمة في الاجتماعات وتنقلها للأمنيين كل أهل إ…
كما قلت مراراً وها هو فيصل القاسم يؤكده الشرع هو من وافق على الاتفاق الأمني كاملاً و على إقامة سلام مع اسرائيل لكن اسرائيل هي من غيرت رئيس الوفد وجمدت الاتفاق بالنسبة لعناصر الهيئة كم وكم تريدون أدلة بعد على أن الشرع هو جاهز لسلام مع اسرائيل ؟
Showing the 12 most recent of 317 posts we hold for @asseraaalsham1. 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.
@asseraaalsham1 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 29 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 55 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 25 October 2026 — this entry's latest reading, not the date you are reading this.
“أس الصراع في الشام” (@asseraaalsham1), 45,174 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/asseraaalsham1.
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.