Telegram RegisterThe public register of Telegram
Telegram profile photo for Aymen Muhammed Official Channel

Channel

Aymen Muhammed Official Channel

@Aymen_Muhammed01

On this record: Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

235subscribers

-1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002742289612
TypeChannel
Username@Aymen_Muhammed01
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/Aymen_Muhammed01

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

235236235.56 August 2026 — 236 subscribers7 August 2026 — 236 subscribers14 August 2026 — 235 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net -1. 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 235–236 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 10:26235-1
7 Aug 2026, 02:46236no change
6 Aug 2026, 20:15236first reading

Engagement

20 posts held, back to 6 June 2026the 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
18.7%
avg views ÷ 235 subscribers
Avg views / post
44.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 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
WindowRolling 30 days · latest post in window 22 July 2026
Posts held20 (6 June 202622 July 2026)
Views total44
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 02:46 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

14 reactions across 13 posts, in 2 distinct kinds. The most used accounts for 78.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1178.6%
321.4%

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 13 of the 20 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 14reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 June 2026 to 22 July 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.

Recent posts

4 Jul 2026, 18:15 UTC≈1,830 views1 reactionsread 7 August 2026

☪️ የረሱል ﷺ የህይወት ታሪክ ☪️ 🔰 ክፍል- ➒⓪ 🔰 ♻️ የስራዊቱን ወኔ ማነሳሳት ======= == ===== 🔰 ትእዛዝ እስኪያስተላልፉ ድረስ ውጊያ እንዳይጀምሩ ወታደሮቻቸውን አዘዙ። ድርብ የጦር ልብስ ለብሰዋል" ለውጊያ አነሳሷቸው እንዲታገሱና እንዲጸኑ አበረታቷቸው። ወኔና የጀግንነት መንፈስ አስረጹባቸው። ስሜታቸውን አቀጣጠሉ፡፡ ሰይፋቸውን መዘዙና፡ ይህን ሰይፍ በተገቢው ሁኔታ የሚይዝ ማን ነው?» በማለት ተጣሩ። በርካታ ሰዎች ተነሱ። ከመካከላቸው ዓሊ ቢን አቢ ጧሊብ፣ ዙበይር ቢን አዋምና ዑመር ቢን አልኸጧብ ይገኙበታል። አቡዱጃናህ ስማክ ቢን ኸርሽህ ቆመና፡ በተገቢው ሁኔታ መያዝ ማለት ምን ማለት ነው?» ሲል ጠ

1

29 Jun 2026, 18:22 UTC≈1,790 viewsread 7 August 2026

🔹 የቁጥር : ልዩነቱን ለማካካስ በጦር | እውቀታቸውና በጀግንነታቸው የሚታወቁ ባልደረቦቻቸውን ከፊት አሰለፉ። በዚህ አኳኋን በሦስተኛው አመተ ሂጅራ በወርሃ ሸዋል ሰባተኛ ቀን በእለተ ቅዳሜ የመልእክተኛው የጦር መሰናዶ ተጠናቀቀ፡፡ @Aymen_Muhammed01

29 Jun 2026, 18:22 UTC≈1,830 views1 reactionsread 7 August 2026

☪️ የረሱል ﷺ የህይወት ታሪክ ☪️ 🔰 ክፍል- ❽➒ 🔰 🔰 የአብደላህ ቢን ኡበይና የባልንጀሮቹ ማፈንገጥ ============================== ◽️ጎህ ከመቅደዱ ጥቂት ቀደም ብለው ተንቀሳቀሱ። «ሸውጥ» ሲደርሱ የሱብሂን ሶላት ሰገዱ። ከጠላት በጣም ቅርብ ነበሩ። እርስ በርስ ይተያዩ ነበር። በዚህ ጊዜ ሙናፊቁ አብደላህ ቢን ኡበይ አፈነገጠ። «ራሳችንን ለሞት አደጋ ለምን እንደምናጋልጥ አናውቅም» በማለት የጦሩን አንድ ሦስተኛ ማለትም ሦስት መቶ ተከታዮቹን ይዞ ለመመለስ ወሰነ። ለዚህ ድርጊት ያቀረበው ምክንያት መልእክተኛው የርሱን ሐሳብ ትተው የሌሎችን አስተያየት ስለተቀበሉ ነው የሚል ነበር። 🔗 እውነተኛው ምክንያ

👍1

27 Jun 2026, 18:27 UTC946 viewsread 7 August 2026

☪️ የረሱል ﷺ የህይወት ታሪክ ☪️ 🔰 ክፍል- ❽➑ 🔰 ♻️ የመከላል እቅድ ለማውጣት የተደረገ ምክክር ============================== 🔹 የመዲና የመረጃ ሐይል የሰራዊቱን እንቅስቃሴ እየተከታተለ መረጃ ያቀርባል። በመጨረሻ መዲና አቅራቢያ መስፈሩን አሳወቀ። በዚህ ጊዜ የአላህ መልእክተኛ ከፍተኛ የወታደራዊ ምክክር ስብሰባ ጠሩ። መወሰድ ስላለበት እርምጃም ሐሳብ ተለዋወጡ" የግል ሐሳባቸውን አቀረቡ። ያዩትንም ሕልም ነገሯቸው። በአላህ እምላለሁ፡ በጎ ሕልም አይቻለሁ፤ ላም ሲታረድና ከሰይፌ ጫፍ ላይ ስብራት አየሁ። ጥብቅ ከሆነ ጡሩራ ውስጥም እጄን ሳስገባ አየሁ።» አሉ። የላሟን መታረድ በጦርነቱ በሚገደሉ ባልንጀሮቻቸ

24 Jun 2026, 18:26 UTC≈1,190 views1 reactionsread 7 August 2026

☪️ የረሱል ﷺ የህይወት ታሪክ ☪️ 🔰 ክፍል- ❽❼ 🔰 🔰 የኡሁድ ዘመቻ ===== ==== ቁረይሾች ለብቀላ ዘመቻ መዘጋጀታ ====== ===== ==== ====== 🔗መካውያን በበድር ሽንፈትና መሪዎቻቸው በመገደላቸው እጅግ ተበሳጭተዋል።እናም ለብቀላ _ ከፍተኛ ዝግጅት ሲያደርጉ ከርመዋል። ማዘናቸውን ሙስሊሞ እንዳያውቁባቸው ሲሉ ሌላ ቀርቶ ለሙታኖቻቸው ማልቀስንና ምርኮኞችን ለማስለቀቅ መፍጠንንም ከልክለዋል። 🔰 የበድር ጦርነት እንደተጠናቀቀ ቁረይሾች በሙስሊሞች ላይ አጠቃላይ የሆነ ጥቃት በመክፈት ለመበቀል ተስማሙ። ለዚህ ጦርነት የሚያስፈልጋቸውን ዝግጅት ሁሉ በስፋት ቀጠሉበት። ኢክሪመት ቢን አቡ ጀህል፣ ሶፍዋን ቢን ኡመያ

👍1

23 Jun 2026, 19:03 UTC52 views1 reactionsread 7 August 2026
Photo

ለሚፆሙ ሁሉ ጠቃሚ ማስታወሻ❗️ ~ የአላህ መልእክተኛ (ሰለላሁ ዐለይሂ ወሰለምእንዲህ ብለዋል፡- ❝ሱሁርን መብላት በረካ አለው፤ ስለዚህ ከእናንተ አንዳችሁ አንዲት ጉንጭ ውሃ እንኳን ቢሆን ሳይጎነጭ እንዳይተወው። ምክንያቱም አላህና መላኢካዎቹ ሱሁር በሚበሉ ሰዎች ላይ ሰለዋት ያወርዳሉ (ዱዓ ያደርጋሉ)።❞ (ሐሰን - ሰሒሕ አል-ጃሚዕ፡ 3683)

1

23 Jun 2026, 18:00 UTC952 views1 reactionsread 7 August 2026

☪️ የረሱል ﷺ የህይወት ታሪክ ☪️ 🔰 ክፍል- ❽❻ 🔰 💭 በአንዲት ጨረቃማ ሌሊት ማለትም በሦስተኛው ዓመተ ሂጅራ በወርሃ ረቢአ አወል 14ኛ ቀን ይህ ቡድን ከመልእክተኛው ዘንድ በመሰባሰብ የመጨረሻ ዝግጅት አጠናቀቀ። የአላህ መልእክተኛም በቂእ አልገርቀድ እስከተባለ ቦታ ሸኟቸው «በአላህ ስም ተጓዙ። አላህ ሆይ! እርዳቸው" አሉና : ወደቤታቸው በመመለስ መስገድና ዱዓ ማድረግ ጀመሩ። 🔗 ቡድኑ ከከአብ ቢን አሽረፍ መኖሪያ ሲደርስ አቡናኢል ጠራው። ከእብ ለመውጣት ሲነሳ ግና ትኩስ ሙሽራ የሆነችው ባለቤቱ በዚህ ሰአት የት ትወጣለህ የሰማሁት ድምጽ ደም የሚንጠባጠብበት የሚመስል ነው፡» አለችው።እርሱም ወንድሜ ሙሐመድ ቢን መስለማህና የጥቢ

👍1

20 Jun 2026, 18:31 UTC875 views1 reactionsread 7 August 2026

አቡናኢልም ልክ እንደ ሙሐመድ ቢን መስለማህ አደረገ፡፡ ከከእብ ጋር ጥቂት ግጥሞችን አነበነበ። ከዚያም፡ «አንድ ጉዳይ ላማክርህ ነው የመጣሁት። ግና በኔና ባንተ ብቻ ይቅር።» አለው። «ይሁን፣ ንገረኝ» የዚህ ሰው መምጣት መከራ ሆነብን፤ ዓረቦች ሁሉ ጠሉን። መንገድ ቆረጡብን። በዚሁ ሰበብም እኛም ቤተሰቦቻችንም ተሰቃየን።አለ" ከሙሐመድ ቢን መስለማህ ጋር ያደረጉትን አይነት ውይይትም አደረጉ" _ አቡናኢል _ በወጉ _ መሐል የሚያስቡ : ባልንጀሮች አሉኝ እንደኔው አመጣቸውና በጥሩ ሁኔታ ትሽጥላቸዋለህ» አለው። 🔰 ኢብን መስለማህና አቡናኢል በዚህ ውይይታቸው ያስቡት ተሳካ። በቀላሉ ባልንጀሮች ለመሆን ቻሉ። ከነርሱ ጋር ሲሆን መሣሪያ አይታጠቅም። @Aymen_M

👍1

20 Jun 2026, 18:31 UTC750 viewsread 7 August 2026

☪️ የረሱል ﷺ የህይወት ታሪክ ☪️ 🔰 ክፍል- ❽❺ 🔰 📍 የሰዊቅ ዘመቻ ==== ==== 📢 ሶፍዋን ቢን ኡመያህ' አይሁዶችና ሙናፊቆች ሴራ በማውጠንጠን ላይ እያሉ አብ ሱፍያን በማሕበረሰቡ ዘንድ ያለውን ቦታ የሚጠብቅና አቅሙን የማያባክን፤ ውጤቱ ፈጣንና በግልጽ የሚታይ፣ ኪሣራው ደግሞ ቀላል የሆነ ጥቃት ለመፈጸም አሰበ በነቢዩ ሙሐመድ ላይ ሳይዘምት በፊት አካሉን ውሃ ላያስነካ ምሎ ነበር። ይህን መሐላውን ለመሙላት ሁለት መቶ ፈረሰኞችን ይዞ ከመዲና አቅራቢያ ከሚገኝ ስፍራ ከኒብ ተራራ አጠገብ ሰፈረ። የቦታው ስም ቀናት» ይባላል። ግና መዲናን በይፋ ለማጥቃት አልደፈረም። የሌባ አይነት ስራ ሰራ። ይኸውም ሌሊት ጨለማን

19 Jun 2026, 18:33 UTC904 views1 reactionsread 7 August 2026

☪️ የረሱል ﷺ የህይወት ታሪክ ☪️ 🔰 ክፍል- ❽❹ 🔰 💢 በኑ ቀይኑቃእ ውሉን ማፍረሳቸው ======== ==== ======== 🔰ግና አላህ ለአማኞች በበድር : ውሎ | የላቀ : ድል : እንዳጎናጸፋቸው ጉልበታቸው እንደበረታ፤ ክብርና ዝናቸውም እንደገነነ ሲመለከቱ ጥላቻቸው ወሰን ጥሶ ገነፈለ። ክፋታቸው ይፋ ወጣ። ግልጽ የጠላትነት ድርጊት ጀመሩ። 🔰 በጠላትነትና በክፋት ከሁሉም የሚብሰው ከእብ ቢን አልአሽረፍ ነበር። እኩይ ድርጊቱ ወደፊት ይጠቀሳል። ከሦስቱ የአይሁድ ጎሳዎች መካከልም ይበልጥ እኩዮች የበኑ ቀይኑቃእ አይሁዶች ነበሩ። መዲና ውስጥ፤ በስማቸው ከሚጠራ ቀዬ ውስጥ ነበር የሚኖሩት። ባለእጆች ስለነበሩ እያ

1

Showing the 12 most recent of 20 posts we hold for @Aymen_Muhammed01. 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,076,669 of 1,563,849entries 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.

Republishes

Channels on the register whose posts this channel has forwarded.

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

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.

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.

“Aymen Muhammed Official Channel” (@Aymen_Muhammed01), 235 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Aymen_Muhammed01.

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.