Telegram RegisterThe public register of Telegram

Channel

lillyStore^

@lillystorely

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

441subscribers

+9 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002833727890
TypeChannel
Username@lillystorely
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/lillystorely

Growth

432441436.58 Aug 2026, 10:30 — 432 subscribers8 Aug 2026, 17:37 — 441 subscribers8 Aug 2026, 10:308 Aug 2026, 17:37
2 measurements taken within a single day, net +9. 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 431–442 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 17:37441+9
8 Aug 2026, 10:30432first reading

Engagement

20 posts held, back to 3 January 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
4.01%
avg views ÷ 441 subscribers
Avg views / post
17.7
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
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 8 August 2026
Posts held20 (3 January 20268 August 2026)
Views total53
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 10:30 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

12 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 41.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
541.7%
👎216.7%
🔥216.7%
😭216.7%
💔18.33%

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 5 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 12reactions 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 3 January 2026 to 8 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.

Advertising

Ad load
15.0%
3 of 20 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
449
over 3 measured posts
Median views · rest
50.0
over 17 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2026010310121458731501030016676725640197413 January 20263 January 2026
2026010610121434581501030016676725680481916 January 20266 January 2026
2026010710121458711501030016676725685197617 January 20267 January 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 20 most recent posts we hold, published 3 January 2026 to 8 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

7 Aug 2026, 13:14 UTC22 viewsread 8 August 2026

🌬 ...“hello, lilies! ❥.. before your story begins within @lillyStorely, let these curated steps unfold like a quiet fairytale upon still waters. each path is arranged with intention, guiding you gently toward a seamless and pleasant ending. sedikit alur ini kami susun agar perjalananmu tetap nyaman dan terarah. 𔘓 〞 ㅤㅤㅤㅤㅤㅤ⸙. catalogue.. 🌬 ㅤㅤㅤㅤㅤㅤ⸙. format order.. 🌬 ㅤㅤㅤㅤㅤㅤ⸙. pembayaran.. 🌬 ㅤㅤㅤㅤㅤㅤ⸙. testimoni.. 🌬 ㅤㅤㅤㅤ୭

18 Jun 2026, 05:13 UTC654 views1 reactionsread 8 August 2026

🍼🍼🍼🍼🍼🍼🍼🍼🍼🍼🍼 cari store yg MURAH?💸 RAMAH?👍 AMANAH?😃 lillystore JAWABANNYA 🤟 murah murah loh 😎 mana tiap pembelian minimal 10k 👅 + subs ch lilly 🐱 dapet free CANVA 1b + VIU 1y 🍑.. apalagi tiap tiap malem sering daget 😱😱 dan mau ngadain GIVEAWAY SALDO 👅 yuk cek pl nya dulu 📌 JAN LUPA CEK PL KEBSOS YAH 😍 MURAH MURAH BGT ITU 🩷 ⭕️⭕️⭕️ APLIKASI PREMIUM netflix 1p1u 1d : 2.000 netflix 1p1u 3d : 5.500 netflix 1p1u 7d : 7.00

1

17 Jun 2026, 07:59 UTC41 viewsread 8 August 2026

📌 PRICELIST TIKTOK 👥 FOLLOWERS LUAR NO GARANSI 100 followers : 4.000 200 followers : 8.000 300 followers : 12.000 400 followers : 16.000 500 followers : 20.000 ▪ akun luar ▪ mix bot & akun asli ▪ followers turun = no garansi 👥 FOLLOWERS LUAR GARANSI 7 HARI 100 followers : 7.000 200 followers : 14.000 300 followers : 21.000 400 followers : 28.000 500 followers : 35.000 ▪ akun luar ▪ mix bot & akun asli ▪ followers t

17 Jun 2026, 07:59 UTC48 viewsread 8 August 2026

📌 PRICELIST INSTAGRAM 👥 FOLLOWERS LUAR NO GARANSI 100 followers : 2.000 200 followers : 4.000 300 followers : 6.000 400 followers : 8.000 500 followers : 10.000 ▪ followers akun luar ▪ mix bot & akun asli ▪ turun = no garansi 👥 FOLLOWERS LUAR GARANSI 30 HARI 100 followers : 4.000 200 followers : 8.000 300 followers : 12.000 400 followers : 16.000 500 followers : 20.000 ▪ followers akun luar ▪ mix bot & akun asli ▪

17 Jun 2026, 07:59 UTC69 viewsread 8 August 2026

📌 PRICELIST TELEGRAM ▶️ SUBS LUAR NO GARANSI 100 subs : 1.000 200 subs : 2.000 300 subs : 3.000 400 subs : 4.000 500 subs : 5.000 ▪ subs akun luar ▪ mix bot & akun asli ▪ turun = no garansi ▶️ SUBS LUAR GARANSI 30 HARI 100 subs : 2.000 200 subs : 4.000 300 subs : 6.000 400 subs : 8.000 500 subs : 10.000 ▪ subs akun luar ▪ mix bot & akun asli ▪ low drop ▪ turun = refill selama garansi ━━━━━━━━━━━━ ? VIEWS NO GARANS

17 Jun 2026, 07:58 UTC62 viewsread 8 August 2026

📌 PRICELIST KEBUTUHAN SOSMED 🎵 TIKTOK 👥 Followers Luar No Garansi 👥 Followers Luar Garansi 7 Hari 👥 Followers Luar Garansi 30 Hari 👥 Followers Indo No Garansi 👥 Followers Indo Garansi 30 Hari ❤️ Like No Garansi ❤️ Like Garansi 30 Hari 👀 View No Garansi 👀 View Garansi 60 Hari 🔄 Share Garansi 30 Hari ━━━━━━━━━━━━ 📸 INSTAGRAM 👥 Followers Luar No Garansi 👥 Followers Luar Garansi 30 Hari 👥 Followers Indo Garansi 30 Ha

Showing the 12 most recent of 20 posts we hold for @lillystorely. 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 — 84,625 of 1,151,006entries 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.

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

“lillyStore^” (@lillystorely), 441 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/lillystorely.

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.