Telegram RegisterThe public register of Telegram

Channel

المري ١ .

@qmarri1

On this record: Growth · Engagement · Posts · Citations · Cite this entry

4,428subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001587820332
TypeChannel
Username@qmarri1
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/qmarri1

Growth

4,4254,4284,426.56 August 2026 — 4,428 subscribers7 August 2026 — 4,426 subscribers10 August 2026 — 4,425 subscribers13 August 2026 — 4,428 subscribers6 August 202613 August 2026
4 measurements spanning 6 days. 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 4,425–4,428 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 07:554,428+3
10 Aug 2026, 18:014,425-1
7 Aug 2026, 20:244,426-2
6 Aug 2026, 22:014,428first 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 6 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
27.2%
avg views ÷ 4,428 subscribers
Avg views / post
1,210
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
7
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 7 August 2026
Posts held20 (6 June 20267 August 2026)
Views total8,441
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 18:14 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.

Recent posts

7 Aug 2026, 15:30 UTC207 viewsread 8 August 2026

مشاريه العيون أبلغ رواية مالها عنوان ‏دخيلك لا تمعنت بعيوني، صد لا تقرا ‏- صالح البرازي

2 Aug 2026, 20:09 UTC604 viewsread 8 August 2026

ثم شفنا الشك والريّبه وعودنا نكايف ‏والرجوع من الدروب العوج نوع من الشطاره . ‏– سفر الدغيلبي

25 Jul 2026, 03:11 UTC≈1,320 viewsread 8 August 2026

صباح الخير ، أما بعد : ‏واجه الخذلان بالصبر .. و البال الطويل ‏ما أنت بـ أول من تجمّل ولا آخر من خُذل

22 Jul 2026, 21:16 UTC≈1,570 viewsread 8 August 2026

حاولت أعدّيها مع الصَدر الوسيع ‏وأرسم على وجه الزَعل وجه الرضا ‏لكن بعض أحيان قلبي ما يطيع ‏بعض الخطأ يضيْق بَه وسع الفضا

21 Jul 2026, 18:04 UTC≈1,590 viewsread 8 August 2026

ماقد تطرقّت الطواري عنك والعالم تشوف ‏ لكنّك أكثر من تربّع وسط عيني و اتضّــح 🩶

19 Jul 2026, 22:15 UTC≈1,620 viewsread 8 August 2026

صباح الخير اما بعد : ‏نطيح من عثرات الأيام ، ونقوم ‏وتزيدنا الطيحه شموخ وكرامه ..

16 Jul 2026, 17:52 UTC≈1,530 viewsread 8 August 2026
Forwarded from @Q_11111Photo

‏وليته لا رحل مثلك حفرنا في السحاب قبور ‏وعشنا في رجا وسمٍ نشوفك في مخاييله .

12 Jul 2026, 15:28 UTC≈1,820 viewsread 8 August 2026

الله يرحم الشيخ حمد بن خليفه ال ثاني

12 Jul 2026, 15:28 UTC≈2,380 viewsread 8 August 2026
Photo

حتى العلم من قوة الصدمه انهار حول وطاح ولا بقى الا .. حديده الله يصبّرنا ويحسن عزاء .. الدار في غيبة اللي والله انه .. فقيده

6 Jul 2026, 15:37 UTC≈1,860 viewsread 8 August 2026

مابين الصعب وبين الخوف والتجريب ‏أحاول ما أميل بيوم ولا تتشرد أفكاري ‏أمرّ بمرحلة صح أو خطا أو صدق أو تكذيب ‏كـأنـي تايـه في شيء ولاني عـارف أقـداري ‏أنا يارب ما ادري وش اللي ينكتب بالغيب ‏ولكن رحمتك أكبر من اللي فيه أنا داري

27 Jun 2026, 09:29 UTC≈2,240 viewsread 8 August 2026

احب التفرّد في زمان المتشابهين ‏حاجةٍ تلهف وراها النّاس — اعوفها

25 Jun 2026, 20:38 UTC≈2,380 viewsread 8 August 2026

من صد صديت لو هو بالغلا كايف ‏ومن راح جعله مراح الطير لا رفرف ‏- ضيدان بن قضعان

Showing the 12 most recent of 20 posts we hold for @qmarri1. 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 — 767,369 of 1,336,469entries 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.

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“المري ١ .” (@qmarri1), 4,428 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/qmarri1.

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.