Sticker, posted without a caption

Channel
львиное божество
@LionDeity
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
27subscribers
-2 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002310279126 |
|---|---|
| Type | Channel |
| Username | @LionDeity |
| Created | Between 1 September 2024 and 21 February 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/LionDeity |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 04:37 | 27 | -2 |
| 28 Aug 2026, 10:07 | 29 | no change |
| 27 Aug 2026, 14:30 | 29 | first reading |
Engagement
17 posts held, back to 21 February 2025 — 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 page of 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 17 posts for this entry, the most recent from 31 August 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 22s
- Average length
- 27s
Measured directly from 3 videos 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.
Reaction mix
429 reactions across 10 posts, in 10 distinct kinds. The most used accounts for 21.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5449415541221512504 | 92 | 21.4% | |
| custom 5260735003683214983 | 80 | 18.6% | |
| custom 5233673471313080030 | 58 | 13.5% | |
| custom 5233734721841686165 | 51 | 11.9% | |
| custom 5235549929639797683 | 37 | 8.62% | |
| custom 5233714681524284703 | 34 | 7.93% | |
| custom 5235884241304183306 | 30 | 6.99% | |
| custom 5235756925588628848 | 28 | 6.53% | |
| custom 5350712992281413780 | 11 | 2.56% | |
| custom 5233491777016588099 | 8 | 1.86% |
Custom emoji. Every row above is a 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 are Telegram’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 17 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 429 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 21 February 2025 to 31 August 2025, 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
- 24
- across the posts below
- Posts paid on
- 5
- of 17 we hold a reading for · 29%
- Most on one post
- 18
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @LionDeity. 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 17 most recent posts we hold for this entry, published 21 February 2025 to 31 August 2025. 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
он скажет "ты под моей защитой", но Чон-Рено говорил: "я в клочья разорву всех, кто ещё раз приблизится к тебе, и та же участь ждёт тех, кто уже сделал это"
custom 526073500368321498311custom 54494155412215125048custom 52358842413041833067custom 52337146815242847035
Sticker, posted without a caption
совсем недавно исполнилась моя мечта, я провёл день в парке львов с этими замечательными малышами. словами всех эмоций не передать.
custom 523371468152428470311custom 54494155412215125049custom 52358842413041833068custom 52607350036832149837
Sticker, posted without a caption
Video, posted without a caption
custom 52358842413041833069custom 54494155412215125049custom 52337146815242847038custom 52607350036832149838
Sticker, posted without a caption
🌟🤩 львёнок.. ты был моим всем. моей бешеной любовью, моей улыбкой, моей мечтой. был моим маленьким счастьем, что радовало меня просто тем, что есть в моей жизни. иногда казалось, что ты воплощение моей больной души, что пыталась излечиться, воображая человека, что дарил тепло, осыпал нежностями. но ты был реальным. мне никто не нужен был, не нужен весь мир, а лишь ты. я изо всех сил старался, становился лучшей верс…
custom 526073500368321498313custom 523371468152428470310custom 54494155412215125047custom 52358842413041833066
Sticker, posted without a caption
🌟 канал львиное божество вновь открывает свои двери. новый набор вз с активом/мью. перед заключением просьба прочитать правила в инфо
custom 535071299228141378011custom 54494155412215125046custom 52607350036832149833
пусть тут будет, шикарно сделано.
custom 523373472184168616510custom 52355499296397976837custom 54494155412215125047custom 52336734713130800304
💕 У тебя новое анонимное сообщение! ↩️ Свайпни для ответа.
custom 523367347131308003017custom 526073500368321498312custom 523373472184168616510
Showing the 12 most recent of 17 posts we hold for @LionDeity. 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.
Forward network
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.
Mentions
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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“львиное божество” (@LionDeity), 27 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/LionDeity.
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.