Telegram RegisterThe public register of Telegram
Telegram profile photo for ل مغوار

Channel

ل مغوار

@L_i_o_4

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

1,655subscribers

-156 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003744154942
TypeChannel
Username@L_i_o_4
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/L_i_o_4

Growth

1,6521,8111,731.57 August 2026 — 1,811 subscribers8 August 2026 — 1,790 subscribers10 August 2026 — 1,652 subscribers13 August 2026 — 1,655 subscribers1,6557 August 202613 August 2026
4 measurements spanning 6 days, net -156. 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 1,628–1,835 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 10:351,655+3
10 Aug 2026, 19:141,652-138
8 Aug 2026, 00:111,790-21
7 Aug 2026, 03:171,811first reading

Engagement

28 posts held, back to 2 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.0%
avg views ÷ 1,655 subscribers
Avg views / post
281
26 posts measured
Reaction rate
1.64%
reactions ÷ views · ER floor
Posts in window
28
of 28 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. It is computed over the 11 of 26 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held28 (2 August 20267 August 2026)
Views total7,299
Reactions total55
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:28 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

55 reactions across 11 posts, in 12 distinct kinds. The most used accounts for 20.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52310243784345866091120.0%
custom 5940489547656732313814.5%
custom 6007921865643790803814.5%
custom 6008310740572708399712.7%
custom 600803329427531844047.27%
custom 532327888867821073935.45%
custom 586148305301616029135.45%
custom 586839061026361075235.45%
👏35.45%
custom 582796791137698466123.64%
💔23.64%
custom 527157715040576356611.82%

Custom emoji. 10 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

Measured over the 28 most recent posts we hold, published 2 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.

Telegram Stars

Stars received
257
across the posts below
Posts paid on
7
of 26 we hold a reading for · 27%
Most on one post
105
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @L_i_o_4. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 28 most recent posts we hold for this entry, published 2 August 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

7 Aug 2026, 16:12 UTC24 viewsread 7 August 2026

يلي معه قناة فعاليات يجي نتبادل اشراف @xx7kh

6 Aug 2026, 23:50 UTC53 views2 reactionsread 7 August 2026

كُنت انظر إليك كمُعجزة لا تأتي بالعمر إلا مرة واحدة ، بينما كُنتَ تراني كشيء يحدث في اليوم ألف مرة [ الله ياخدك ]

💔2

6 Aug 2026, 17:01 UTC83 views4 reactions10 Starsread 7 August 2026

"وبدأ تنافس الصالحين بكثرة الصلاة على النبي 📿 في ليلة الجمعة ويومها، فلا تجعل نصيبك منه قليل، وتذكر أنًّ بكل صلاة على النبي 📿 يُصلِّي الله عليك بها عشرًا، وترفع عشر درجات، ويُحط عنك عشر خطيئات“. ▫️ صلوا على الحبيب 📿 وأكثروا."

custom 60079218656437908034

6 Aug 2026, 07:56 UTC192 views1 reactions12 Starsread 7 August 2026

تشويه السمعة ، وتأليف القصص الكاذبة وسيلة يستخدمها الحاقدين والفاشلين من اجل التقليل من قيمة الاخرين .

custom 58614830530161602911

6 Aug 2026, 02:35 UTC271 views5 reactionsread 7 August 2026

سحب 300 نجمه

custom 52310243784345866095

Signed مغوار

6 Aug 2026, 02:34 UTC236 viewsread 7 August 2026

سحب على 300 نجمه شترك ووجه • روليت تناهيد > جميع السحوبات

Signed روليت تناهيد

Showing the 12 most recent of 28 posts we hold for @L_i_o_4. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 221,328 of 1,480,944entries 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

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 6 registered channels — 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.

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

“ل مغوار” (@L_i_o_4), 1,655 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/L_i_o_4.

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.