10 measurements spanning 33 days, net +1,141. 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 79โ6,309 and does not start at zero.
Measurement log โ every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
9 Sept 2026, 16:36
1,939
-5
4 Sept 2026, 04:17
1,944
-5
31 Aug 2026, 11:43
1,949
-22
28 Aug 2026, 19:45
1,971
-10
25 Aug 2026, 12:03
1,981
-423
22 Aug 2026, 11:04
2,404
-3,010
18 Aug 2026, 21:55
5,414
-176
15 Aug 2026, 18:02
5,590
+4,792
8 Aug 2026, 01:36
798
no change
7 Aug 2026, 18:12
798
first reading
Engagement
12 posts held, back to 5 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 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 12 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
45 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 31.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
๐ฏ
14
31.1%
๐ฅ
14
31.1%
๐
13
28.9%
โค
2
4.44%
โคโ๐ฅ
1
2.22%
๐
1
2.22%
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 12 of the 12 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 45 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 12 most recent posts we hold, published 5 August 2026 to 7 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.
Showing the 12 most recent of 12 posts we hold for @mohammed963abowaleed. 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.
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 9 September 2026 โ this
entry's latest reading, not the date you are reading this.
โ๐ฑ ุฐุฆุงุจ ุงูุชุฏุงูู ABO_WALEED๐ฑโ (@mohammed963abowaleed), 1,939 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/mohammed963abowaleed.
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.
