Channel
@Likysek666
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
352subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001883327853 |
|---|---|
| Type | Channel |
| Username | @Likysek666 |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Likysek666 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 11:23 | 352 | +6 |
| 8 Aug 2026, 00:42 | 346 | +1 |
| 7 Aug 2026, 03:16 | 345 | first reading |
19 posts held, back to 12 July 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.
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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 19 (12 July 2026 – 6 August 2026) |
| Views total | 6,069 |
| Reactions total | 875 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 03:16 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.
1,089 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 34.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 374 | 34.3% | |
| custom 5195387900908294256 | 223 | 20.5% | |
| custom 5266968624727341424 | 199 | 18.3% | |
| custom 5192902493528412574 | 192 | 17.6% | |
| custom 5427152797286015811 | 59 | 5.42% | |
| custom 5310262264438218323 | 25 | 2.30% | |
| custom 5344024220668040738 | 17 | 1.56% |
Custom emoji. 6 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 19 of the 19 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 1,089reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 12 July 2026 to 6 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Likysek666. 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 19 most recent posts we hold for this entry, published 12 July 2026 to 6 August 2026. 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.
ангст кассберги этт после конца мистики буду рада рт, коммам и реакциям!! #полноценка #никитаберг #кассандра
custom 519538790090829425632custom 534402422066804073813custom 54271527972860158118❤2custom 51929024935284125741
ааа 3 августа страшно вырубай буду рада рт, реакциям и коммам! #полноценка #никитаберг #мимик
❤43custom 519538790090829425620custom 519290249352841257414custom 53440242206680407384custom 54271527972860158112
ос ликусека 🤩 #скетч
custom 519290249352841257418❤10
ура я всех дорисовала ахуеннок качество шакал ебучий если что у ангелов и демоническтх/мистическтх сущностей биология другая, ангелы вообще живут бесконечно долго. им может быть много лет, но при этом выглядеть молодо (111 лет ангела = 23 года наших, 174 года ангела = 32 года, 55 лет ангела = 15 лет) лилит- мать вячи арагат - отец вячи рафаила - бывшая подруга вячи (на момент нахождения на континенте ангелов) кай -…
❤24custom 51953879009082942567custom 51929024935284125744
я зеабелесь рисоваьь его краткого лора нет я не придумала #морган #ос
custom 519538790090829425628custom 53102622644382183237custom 51929024935284125746❤5
ребят я редизайнула его если что я фото уже заменила и в после уже редизайн
❤21custom 54271527972860158111
ромберги для души буду рада рт, реакциям и коммам! #полноценка #никитаберг #роменский
custom 519538790090829425658custom 542715279728601581121custom 519290249352841257415❤9custom 53102622644382183232
🤍Гифт для Ликусека🤍
custom 519538790090829425622❤7custom 51929024935284125746custom 53102622644382183233
коллаба шарплов шарпнесс @Likysek666 (я) джудлоу @strbebbofc #коллаб #шарпнесс #полноценка
custom 519538790090829425644❤18custom 519290249352841257410custom 53102622644382183232custom 54271527972860158111
напоминаю что заказы беру ВОЗБМУ 5 СЛОТОВ!!
❤23custom 51929024935284125742custom 51953879009082942562
я первая кто нарисовала его хохоо буду рада активности любой #никитаберг #скетч
❤48custom 519290249352841257419custom 519538790090829425610custom 54271527972860158115custom 53102622644382183231
шарнесс wolf буду рада репостам, реакциям и коммам! #полноценка #шарпнесс
custom 526696862472734142457❤25custom 519290249352841257412custom 54271527972860158118custom 53102622644382183231
Showing the 12 most recent of 19 posts we hold for @Likysek666. 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 — 123,646 of 1,478,351entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 4 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Likусек” (@Likysek666), 352 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Likysek666.
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.