2 measurements spanning 1 day. 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 472–474 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 03:58
473
no change
13 Aug 2026, 03:31
473
first reading
Engagement
19 posts held, back to 2 July 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
24.3%
avg views ÷ 473 subscribers
Avg views / post
115
7 posts measured
Reaction rate
8.45%
reactions ÷ views · ER floor
Posts in window
7
of 19 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
Window
Rolling 30 days · latest post in window 10 August 2026
Posts held
19 (2 July 2026 – 10 August 2026)
Views total
805
Reactions total
68
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
13 Aug 2026, 03:31 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.
Reaction mix
204 reactions across 19 posts, in 5 distinct kinds. The most used accounts for 63.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
129
63.2%
💔
59
28.9%
😢
11
5.39%
💯
3
1.47%
😭
2
0.98%
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 19 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 204reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 2 July 2026 to 10 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.
ذِكرى الأَنَس!!
صوتُ غزّة وابنها البار...
غُيّبت غزّة من بعدك يا أنس!
وذُبحت من الوريد إلى الوريد، دون صوتك الذي بُحَّ وأنت تنقل وجعها إلى العالم.
قُتلت غزّة باغتيالك...
وسقطت أقنعةُ كثيرٍ من المتسلّقين على ظهرها، أولئك الذين طالما احتموا بوجعها وتزيّنوا باسمها.
باتت غزّة كحسناءَ تُذبح بصمت، في زاويةٍ أعمى الجميع عنها عينه، وتواطأ الصمت على إخفاء جرحها.
تبكيك غزّة يا أنس،
ويبكيك معها أحرار العالم جميعًا؛
فما كنتَ…
أكبر جنازةٍ في تاريخ فلسطين... وأكبر وصمةِ خِزيٍ في جبين هذه الأمة.
اليوم، وبعد ما يقارب ثلاثة أعوام على مجزرةٍ ارتقى فيها أكثر من 300 شهيد، كان معظمهم من النساء والأطفال، يُشيَّع مائةُ شهيدٍ فقط من أصل ذلك العدد، بعدما ظلّت أجسادهم تحت الركام كل هذه السنين.
لم يُنتشل رفاتهم بآلياتٍ أو فرق إنقاذ، بل بأيدي ذويهم الذين نقّبوا بأظافرهم بين الحجارة والتراب؛ يبحثون عن بقايا أحبتهم ليكرموهم بدفنٍ يليق بكرامتهم.
أيُّ زمن…
﴿وَيَمْكُرُونَ وَيَمْكُرُ اللَّهُ ۖ وَاللَّهُ خَيْرُ الْمَاكِرِينَ﴾
مكر حفدةُ القردةِ بسيدنا عيسى عليه السلام، فرفعه الله إليه، ويمكرون اليوم ومعهم منافقو عصرنا بحملة لواء محمد ﷺ، والله ناصرهم ووليُّهم، وهو ربُّهم، وبه قوّتُهم وثباتُهم.
أتخافون على هذه الحركة الطيبة؟
أتخافون على من بايعوا الله على النفس والمال والولد؟
بل خافوا على أنفسكم إن كنتم صادقين.
أمّا أولئك فلا خوفٌ عليهم ولا هم يحزنون؛ هم تحت كنف الله وعنا…
يُقتحمُ المسرى بآلافِ الأنجاس، ويتكرّر المشهدُ يومًا بعد يوم، حتى غدا الخبرُ لا يحظى إلا بمرورٍ عابر، يختبئ بين شريطِ الأخبار العاجلة، ثم يُطوى وكأن شيئًا لم يكن.
وأسفاااه ! كيف بلغ بأمّةٍ كان الأقصى قضيّتَها أن يمرَّ خبرُ تدنيسِه فلا يحرّك فيها غيرةً، ولا يوقظ لها وجعًا؟
لكن لا عجب...
فمن خذل الأسرى، وخذل حرّاسَ الأقصى، وسكت ثلاثةَ أعوامٍ على أشلاءِ غزة ودمائها، لا يُستغرَب عليه أن يخذل المسرى، وأن يجعل اقتحامَه خ…
ليست دماءُ أضاحي، بل دِماءُ أرواحٍ طاهرة أُزهِقت في سبيلِ الله، ونحنُ على خِذلانِهم شُهود؛
فيا ويحنا حين نقفُ بين يدي عدلٍ قهّار ونُسألُ عن كلّ قطرةٍ منها.
تفحّمت أجسادُهم في الدُّنيا!
وهان ذلك أنّه في سبيلِ ربٍّ أحبُّ إلينا من كلّ شيء؛
يارب إنّا نُشهِدُكَ أن أجسادَهم قد تفحّمت في سبيلك ورفع كلمتك - وأنت أعلم -، فاللهُمَّ حرّم عنهم نار الآخرة برحمتك، وارفعهم إلى الفردوس الأعلى من الجنة، وأنسِهم مرارة الدنيا وكدرها.
كانتِ البلادُ ظلَّه، وكانتِ القُدسُ قلبَه.
عاش بصمت، وجاهد بصمت، وارتقى بصمت.
رجلٌ أدرك أن الفلاحَ في الإخلاص، وأن التجارةَ الرابحةَ هي مع الله لا مع الناس، وأن الغايةَ كلَّ الغايةِ أن يرضى عنه العظيمُ في علاه.
رحل عن الدنيا بصمت، ليُذكّر أُمَّة الإسلامِ بأن ما كان لله يبقى.
- الذكرى الثانية لاستشهاد حامل اللواء المُحمّدي.
وألوذُ بكَ من حولي وضعفي إلى حولك وقوّتك، ومن ضيق تفكيري إلى سَعَة تدبيرِك.
"لا إله إلا الله العظيم الحليم، لا إله إلا الله ربّ العرش العظيم، لا إله إلا الله رب السماوات ورب الأرض ورب العرش الكريم".
إلى ذلك المُنشغل بمُباريات كأس العالم المُسيّس..
هل تعلم أن أُمَّهاتِنا في غزّة يحملنّ ما تبقّى من رُفات أبنائهنّ الشهداءِ بأيديهنّ؟
حسبنا الله ونعم الوكيل، حسبنا الله ونعم الوكيل.
Showing the 12 most recent of 19 posts we hold for @Allah_ghaiti. 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
Citation-graph rank — 1,149,599 of 1,189,255entries 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.
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
Names
Channels on the register whose handles appear in this channel's posts.
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 14 August 2026 — this
entry's latest reading, not the date you are reading this.
“اللَّهُ غَايَتُنَا.” (@Allah_ghaiti), 473 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Allah_ghaiti.
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.