увы поста не будет, возможно на рест…
Signed LilYAqqeshk_.

Channel
@LilyaqqeHelp
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
23subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004364140450 |
|---|---|
| Type | Channel |
| Username | @LilyaqqeHelp |
| Description | начало: 24.06.26. |
| Created | Between 1 June 2026 and 25 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/LilyaqqeHelp |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 12:18 | 23 | no change |
| 10 Aug 2026, 21:45 | 23 | first reading |
18 posts held, back to 25 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 5 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
116 reactions across 11 posts, in 15 distinct kinds. The most used accounts for 19.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5294206796217477153 | 22 | 19.0% | |
| custom 5190529657241363006 | 14 | 12.1% | |
| 💘 | 12 | 10.3% | |
| custom 5242709760381301216 | 11 | 9.48% | |
| custom 5312542273597087206 | 9 | 7.76% | |
| custom 5244844311882790779 | 8 | 6.90% | |
| custom 5404361428775761041 | 8 | 6.90% | |
| custom 5244535198791532367 | 7 | 6.03% | |
| custom 5285069648432227199 | 7 | 6.03% | |
| custom 5310162810175496382 | 5 | 4.31% | |
| custom 5323682851827257351 | 4 | 3.45% | |
| custom 5242607608879133045 | 3 | 2.59% | |
| custom 5323338013198030552 | 3 | 2.59% | |
| custom 5433627877096579974 | 2 | 1.72% | |
| custom 5424586051815502630 | 1 | 0.862% |
Custom emoji. 14 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 18 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 116reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 25 June 2026 to 5 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.
увы поста не будет, возможно на рест…
Signed LilYAqqeshk_.
Sticker, posted without a caption
Signed LilYAqqeshk_.
🫀🫀😇🔠🔠🔠🔠🔠🔠🔠😇🫀🫀 😀😀😀😀😀 ➖➖🤩🤩 #дрейк #пак #коллаб 😇😇 ⭐😀😀😀😀😀 🔤🔤: @aaangelllls ✖️ @LilyaqqeHelp 🤩🤩 Авы - 11 Обои - 13 Баннеры - 26 Прем эмодзи - 64⭐⭐🤍🤍🤍⭐⭐ 🤩🤩🌟 ⲙᥲⲧᥱρυᥲ᥈ ⲃ ⲕ𐔖ⲙⲙ🌟
custom 54336278770965799742
Signed LilYAqqeshk_.
Sticker, posted without a caption
Signed LilYAqqeshk_.
🤩🤩➖➖➖➖➖➖ 🌟🌟🌟🌟🌟🌟🌟🌟 🌟🌟🗿 Drake — 💜 ⊹ . ✧ . ⸝⸝ 104 emoji ➖➖➖⊹➖➖✧➖🤩🤩 lilyaqqe
custom 52448443118827907798custom 54043614287757610418custom 52445351987915323677custom 53236828518272573514custom 53233380131980305523
Signed LilYAqqeshk_.
Sticker, posted without a caption
Signed LilYAqqeshk_.
⭐⭐🌟arried ⭐⭐⭐⭐🌟etween ⭐️@ssvarkkaj0 & @LilyaqqeHelp ⭐️🔠eel me, ŵaiť, я буду вы🕋ше 🤩🤩я управляю мир0м через ➖➖➖➖ аpple Vision ⭐️🪦🔹а мне лишь чěрĦый kапюш0H, и я б🌟гу по 🐈🛼🤪🎱🦄 ⭐️⭐️⭐️ты сно💲ва çпрøčишь меня, чŤ0 мной дв🌟жет 🔤🔤🔤? 🪦🔹ожешь, не обм🌟нывать, я всё равно увижу ⭐⭐твои импульсы по т💲лу, и я слышу, как ты дышишь ⭐🔤еребираю рук🌟ми, ищу что-то пøблűжě ⭐⭐⭐🔤е та, сĦøвǎ не та, но это бу🌟ет Ťőчнø ➖➖➖➖➖, чем 🪦чёPная 🔤…
custom 52426076088791330453custom 53125422735970872063💘2custom 52942067962174771532custom 51905296572413630061custom 52427097603813012161
Signed LilYAqqeshk_.
Sticker, posted without a caption
Signed LilYAqqeshk_.
Sticker, posted without a caption
Signed LilYAqqeshk_.
🤩🤩 ligaments 🪦➖🪦☦️🌟🩷➖🪦❤️ #Drake 🌟quantity; 10 !!material in the comments!! lilyaqqe
custom 51905296572413630064custom 52427097603813012164custom 52942067962174771534custom 53125422735970872064💘1
Signed LilYAqqeshk_.
Sticker, posted without a caption
custom 54245860518155026301
Signed LilYAqqeshk_.
🤩🤩premium - pack 🪦➖🪦🤩🪦➖➖🤩🪦 #TheBrianMaps 🌸TheBrianMaps 🫀40 stickers lilyaqqe
custom 51905296572413630066💘5custom 52850696484322271995custom 52942067962174771533
Signed LilYAqqeshk_.
Showing the 12 most recent of 18 posts we hold for @LilyaqqeHelp. 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 — 1,319,036 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.
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.
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.
@LilyaqqeHelp named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Рест, не рп — ``lilyaqqe _ help . . ‘’” (@LilyaqqeHelp), 23 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/LilyaqqeHelp.
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.