Telegram RegisterThe public register of Telegram
Telegram profile photo for L

Channel

L

@stikery05

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Cite this entry

18subscribers

-2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002363858843
TypeChannel
Username@stikery05
Created16 February 2025measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live29 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 29 August 2026
On Telegramt.me/stikery05

Growth

1820197 August 2026 — 20 subscribers11 August 2026 — 20 subscribers15 August 2026 — 19 subscribers21 August 2026 — 18 subscribers7 August 202621 August 2026
4 measurements spanning 14 days, net -2. 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 18–20 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 23:4618-1
15 Aug 2026, 08:3519-1
11 Aug 2026, 15:4620no change
7 Aug 2026, 14:5520first reading

Engagement

5 posts held, back to 16 February 2025the 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 5 posts for this entry, the most recent from 21 July 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
12s
Average length
12s

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.

Reaction mix

394 reactions across 4 posts, in 19 distinct kinds. The most used accounts for 38.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🌚15038.1%
🔥7920.1%
❤‍🔥348.63%
297.36%
custom 5226569569635688451194.82%
💘174.31%
custom 5273928778144304576164.06%
🕊133.30%
custom 545398275360950142592.28%
custom 539565561167114965882.03%
custom 523373548205090160551.27%
custom 542708638420672808141.02%
custom 522688127259222586830.761%
custom 526722263768317750220.508%
custom 537294342517792043020.508%
custom 533922517024036377510.254%
custom 539573087667804369610.254%
custom 541587822896115662010.254%
custom 602833854673610766810.254%

Custom emoji. 13 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 4 of the 5 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 394reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 16 February 2025 to 21 July 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
15
across the posts below
Posts paid on
1
of 4 we hold a reading for · 25%
Most on one post
15
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @stikery05. 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 5 most recent posts we hold for this entry, published 16 February 2025 to 21 July 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

21 Jul 2025, 19:58 UTC≈1,620 views28 reactionsread 11 August 2026
Sticker

Sticker, posted without a caption

custom 527392877814430457614custom 54539827536095014259custom 54270863842067280814custom 52265695696356884511

21 Jul 2025, 19:58 UTC≈1,590 views21 reactionsread 11 August 2026
Sticker

Sticker, posted without a caption

custom 522656956963568845110custom 53956556116711496588custom 52672226376831775022custom 53957308766780436961

21 Jul 2025, 19:57 UTC≈1,570 views22 reactionsread 11 August 2026
Photo

во всех чатах, в которых я присутствую - не имею никакого отношения

12custom 52265695696356884515custom 52268812725922258683custom 53392251702403637751custom 60283385467361076681

16 Feb 2025, 19:42 UTC≈2,440 views323 reactions15 Starsread 11 August 2026
Video

.

🌚150🔥79❤‍🔥3417💘17🕊13custom 52337354820509016055custom 52265695696356884513

Showing the 5 most recent of 5 posts we hold for @stikery05. 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.

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

“L” (@stikery05), 18 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/stikery05.

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.