Channel
@LLSKRC
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
8subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001600735948 |
|---|---|
| Type | Channel |
| Username | @LLSKRC |
| Description | 🐊🐊🐊 |
| Created | 5 April 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/LLSKRC |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 15:18 | 8 | no change |
| 7 Aug 2026, 19:54 | 8 | first reading |
20 posts held, back to 12 January 2024 — 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 20 posts for this entry, the most recent from 5 March 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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 7 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.
136 reactions across 11 posts, in 27 distinct kinds. The most used accounts for 12.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5246766627575316409 | 17 | 12.5% | |
| custom 5249483516512584873 | 16 | 11.8% | |
| custom 5307553162276652548 | 11 | 8.09% | |
| custom 5249266968556486116 | 10 | 7.35% | |
| custom 5249123091447040715 | 8 | 5.88% | |
| custom 5458425781313093726 | 8 | 5.88% | |
| custom 5384589125921812392 | 7 | 5.15% | |
| custom 5395528441984466168 | 6 | 4.41% | |
| custom 5458851099039512343 | 6 | 4.41% | |
| custom 5211015001975832030 | 5 | 3.68% | |
| custom 5460714762658656905 | 5 | 3.68% | |
| ❤🔥 | 5 | 3.68% | |
| custom 5208693993059141108 | 4 | 2.94% | |
| custom 5242370522389428993 | 3 | 2.21% | |
| custom 5244676636359536844 | 3 | 2.21% | |
| custom 5359805760169584717 | 3 | 2.21% | |
| custom 5384276039985805020 | 3 | 2.21% | |
| custom 5384610721017376720 | 3 | 2.21% | |
| custom 5213195900469391739 | 2 | 1.47% | |
| custom 5370605713133412674 | 2 | 1.47% | |
| 7 further kinds | 9 | 6.62% |
Custom emoji. 19 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 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 136reactions 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 12 January 2024 to 5 March 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Video, posted without a caption
custom 52467666275753164093custom 53075531622766525483custom 52492669685564861162custom 52494835165125848732custom 53955284419844661682custom 52491230914470407151custom 54584257813130937261
Signed elliss.?
🌟🌟
custom 52494835165125848734custom 53075531622766525483custom 52467666275753164092custom 52491230914470407152custom 54584257813130937262custom 52492669685564861161custom 53955284419844661681
Signed elliss.?
Video, posted without a caption
custom 52467666275753164094custom 52491230914470407153custom 52494835165125848732custom 54584257813130937262custom 52492669685564861161custom 53955284419844661681
Signed elliss.?
любимка сделала🌟🤩
custom 52467666275753164093custom 52494835165125848733custom 53075531622766525483custom 52492669685564861162custom 52086939930591411081custom 53955284419844661681custom 54584257813130937261
Signed elliss.?
Video, posted without a caption
custom 52467666275753164094custom 52086939930591411083custom 52492669685564861163custom 52494835165125848733custom 54584257813130937262custom 53955284419844661681custom 54607784054840526811
Signed elliss.?
Video, posted without a caption
custom 53598057601695847173custom 53845891259218123923❤🔥2custom 52491230914470407152custom 52494835165125848732custom 53075531622766525482💘1custom 52467666275753164091
Signed elliss.?
Channel name was changed to «ellisskkaa»
Channel photo updated
ну да
Signed elliss?
У тебя новое анонимное сообщение! элис-нефор ↩️ Свайпни для ответа.
custom 54588510990395123434👻1
Signed elliss?
это я
Signed SMOKE IT OFF
интересно
Signed elliss?
Showing the 12 most recent of 20 posts we hold for @LLSKRC. 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.
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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“ellisskkaa” (@LLSKRC), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/LLSKRC.
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.