Channel
@lilyscent1
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
834subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002238096355 |
|---|---|
| Type | Channel |
| Username | @lilyscent1 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/lilyscent1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 22:29 | 834 | -3 |
| 7 Aug 2026, 15:44 | 837 | no change |
| 7 Aug 2026, 06:45 | 837 | first reading |
20 posts held, back to 5 June 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 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.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 20 (5 June 2026 – 4 August 2026) |
| Views total | 631 |
| Reactions total | 55 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 06:45 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.
316 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 40.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5870487932988560659 | 129 | 40.8% | |
| custom 6008029991445468229 | 77 | 24.4% | |
| custom 5974295853718838416 | 51 | 16.1% | |
| 😢 | 22 | 6.96% | |
| custom 5902499432347212039 | 20 | 6.33% | |
| custom 6030397120266116210 | 17 | 5.38% |
Custom emoji. 5 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 20 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 316reactions 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 5 June 2026 to 4 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @lilyscent1. 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 20 most recent posts we hold for this entry, published 5 June 2026 to 4 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.
«وَاخْتَرْ لِنَفْسِكَ مَنْزِلًا تَعْلُو بِهِ، أَوْ مُتْ كَرِيمًا تَحْتَ ظِلِّ الْقَسْطَلِ. فَالْمَوْتُ لَا يُنْجِيكَ مِنْ آفَاتِهِ، حِصْنٌ وَلَوْ شَيَّدْتَهُ بِالْجَنْدَلِ.»
custom 58704879329885606599
Signed sarah
حالتي الصحية في تدهور لطفًا ادعوا لي بالشفاء
😢22custom 587048793298856065914custom 600802999144546822910
Signed sarah
دعواتكم لأبوي بالشفاء العاجل 🤔
custom 587048793298856065913custom 60080299914454682297
Video, posted without a caption
custom 587048793298856065912
🎀 • «إِنِّي أخشى أن تَلهوَ بي الحياةُ، فأنسى حُفرةً سأكونُ بها يومًا، فيا ربِّ، كُلَّما رأيتني أبتعدُ عنك، رُدَّني إليك ردًّا جميلًا 💖.»
custom 59742958537188384169custom 60080299914454682292
Video, posted without a caption
custom 58704879329885606599custom 60080299914454682292
لا حول ولا قوة إلا بالله العلي العظيم دعواتكم لابوها بالرحمه والمغفرة
custom 600802999144546822914custom 58704879329885606594
ادعو ربي يربط على قلبها وادعو لابوها بالرحمه💞
custom 600802999144546822918custom 58704879329885606592
Photo, posted without a caption
custom 59024994323472120397custom 58704879329885606593custom 60303971202661162103
«ولا تُعذِّبني بقبيحٍ ما تعلمُ به مِنِّي، فإنَّ عفوَكَ وجودَكَ يَسَعُني.»
custom 59742958537188384169
الله يسعدك خليهم يدعون لي تطلع درجتي بالتحصيلي مية، لعل احدكم اقرب إلى الله مني 💓
custom 600802999144546822915custom 58704879329885606595
Photo, posted without a caption
custom 587048793298856065911
Showing the 12 most recent of 20 posts we hold for @lilyscent1. 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 — 953,376 of 1,480,975entries 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.
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.
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.
“وَهَج” (@lilyscent1), 834 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/lilyscent1.
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.