Channel
@alnadam3
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
11,591subscribers
-41 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001585195221 |
|---|---|
| Type | Channel |
| Username | @alnadam3 |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/alnadam3 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 18:53 | 11,591 | -14 |
| 14 Aug 2026, 05:17 | 11,605 | -11 |
| 12 Aug 2026, 20:53 | 11,616 | -4 |
| 11 Aug 2026, 21:03 | 11,620 | -3 |
| 10 Aug 2026, 19:55 | 11,623 | -1 |
| 9 Aug 2026, 22:31 | 11,624 | -8 |
| 9 Aug 2026, 19:16 | 11,632 | first reading |
33 posts held, back to 2 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 9 pagesof 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 15 August 2026 |
|---|---|
| Posts held | 33 (2 August 2026 – 15 August 2026) |
| Views total | 30,269 |
| Reactions total | 465 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 15:27 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.
465 reactions across 33 posts, in 3 distinct kinds. The most used accounts for 67.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💔 | 312 | 67.1% | |
| ❤ | 131 | 28.2% | |
| 😢 | 22 | 4.73% |
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 33 of the 33 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 465reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 33 most recent posts we hold, published 2 August 2026 to 15 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.
دموعُ الفرحة عني غائبة.. مُنذ سنوات بعيدة لم تذرف عيني من الفرحة، لم أتنهد تنهيدة الراحة بعد حصولي على شيءٍ تمنيته، لم تتسارع دقات قلبي من خبر سار يأتيني فجأة، الأمر أصبح عاديًا جدًا، تشابهت كل الأشياء بداخلي، وتمادت الأيام في مواصلة أحداثها المُتشابهة🖤!..
💔6
لم يَتغيّر فجأة لكنّ شيئًا ما في داخله انطفأ بهدوء فما عادت الأشياء تعنيهُ كما كانت ولا الأشخاص يملكون المكانة ذاتُها صَار أبرد من أن يُعاتب وأهدأ من أن يشرح وكأن قلبه تعلّم أخيرًا ألّا يشعر كثيرًا🖤!...
💔8❤2
🖤!...
💔3
.إن رغبتي الوحيدة هي أن تكون سعيداً أنت تعرفُ ذلك جيداً، إنني مذعنة لقدري، لكن قلبي سيظلُ معكَ دائماً🖤!...
💔9❤4
تظُن أنك تعودت.. لكنك تعود لتبكي للسبب نفسه، فتدرك أن جزءًا منك مازال عالقًا في المكان الذي تأذى فيه أول مرة وأن بعض الأشياء لم تتجاوزها حقًا، أنت فقط تعلمت كيف تعيش وهي بداخلك🖤!..
💔11❤5
كيفَ أنجُو مِن خيالٍ فاضَ بِالذكرى القَديمة🖤!..
💔12
عليك أن تتقبل أن بعض البشر سيحتلون مكاناً في قلبك إلى اﻷبد دون أن يكون لهم مكان في حياتك🖤!...
😢9❤5💔4
«للأسف أنا مش بعرف أتخطّى غياب حد كان يوم جزء من حياتي بسهولة.. أنا بتعلّق بالناس زيادة عن اللزوم، وبرحيلهم بسيب جزء مني معاهم. العِشرة عندي مش سهلة، والذكريات مش بتتمسح، والأيام اللي عشناها سوا مش بعرف أعتبرها كأنها مكنتش. يمكن دي أكتر حاجة بتتعبني.. إني بعرف أحب بجد، بس مبعرفش أخرج حد من قلبي بسهولة. وعشان كده.. أنا آخر واحدة ممكن يهون عليها غياب حد كان يوم غالي عليها🖤!..
💔12❤3
ولا زلت أطرح نفس السؤال كيف ستكون نهايتي.؟ أنا من قضيت عمراً بأكمله تخذلني جميع الطرق🖤!...
💔7❤3😢3
5555
💔4
أما عني، فأنا لستُ بخير، أنا فقط أحيا، ليس كما يجب أن يحيا الناس، كل ما أعرفه أني أحيا. مريض، ممتلئ بالأزمات، أعاني ليلاً فكلما أظلمت كلما أمطرت سماي وجاش فيّ العويل. أنا لستُ بخير أقسم، باهت للغاية، هزيل، قتيلٌ حي وأتنفّس ودادي زفير. أنا لستُ بخير لُطفًا دسوني بين دعواتكم🖤!...
💔11❤4
أشعرُ أنَّ هُنالك خيبة، عالقةٌ في مُنتصفِ المَرىء تُسبب إرتجاع الذكريات 🖤..!
❤11💔3
Showing the 12 most recent of 33 posts we hold for @alnadam3. 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 — 1,264,622 of 1,480,688entries 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.
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 1 seed channel's Telegram-generated recommendation list 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“الندم_alnadam🖤” (@alnadam3), 11,591 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/alnadam3.
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.