( 🌟🌟 ) :: привет, на связи совладелец! хочу вас спросить, какие бы вы хотели видеть интерактивы? может, у вас есть идеи?
❤9🔥2custom 52062312888764043411custom 54047135946192082421custom 62331565906654745721

Channel
@YesIkinnLCB
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
186subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003525228464 |
|---|---|
| Type | Channel |
| Username | @YesIkinnLCB |
| Created | Between 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/YesIkinnLCB |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 22:04 | 186 | no change |
| 12 Aug 2026, 15:02 | 186 | first reading |
20 posts held, back to 22 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 20 posts for this entry, the most recent from 15 July 2026. An engagement rate over an empty window would be a number about nothing.
248 reactions across 19 posts, in 15 distinct kinds. The most used accounts for 24.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5206231288876404341 | 60 | 24.2% | |
| custom 5404769738431701726 | 43 | 17.3% | |
| custom 5404874982310325242 | 26 | 10.5% | |
| custom 6233156590665474572 | 26 | 10.5% | |
| 😨 | 22 | 8.87% | |
| custom 6233101503414935427 | 15 | 6.05% | |
| ❤ | 15 | 6.05% | |
| custom 6145584797365311708 | 14 | 5.65% | |
| custom 5404713594619208242 | 10 | 4.03% | |
| 👍 | 5 | 2.02% | |
| custom 5454149707578253314 | 4 | 1.61% | |
| ❤🔥 | 3 | 1.21% | |
| 🔥 | 2 | 0.806% | |
| 🕊 | 2 | 0.806% | |
| 🤝 | 1 | 0.403% |
Custom emoji. 8 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 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 248reactions 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 22 June 2026 to 15 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.
( 🌟🌟 ) :: привет, на связи совладелец! хочу вас спросить, какие бы вы хотели видеть интерактивы? может, у вас есть идеи?
❤9🔥2custom 52062312888764043411custom 54047135946192082421custom 62331565906654745721
ㅤㅤㅤ🤩⪩ִ𓍢𓍢ࣩ 🤩Главный кинн Сан И это . . . ㅤㅤㅤㅤㅤ🥹🥹🥹@amironos! 🥹🥹 ㅤㅤㅤㅤㅤ @YesIkinnLCB | #MainKinn
custom 52062312888764043415🕊2custom 62331015034149354272
ㅤㅤㅤ🤩⪩ִ𓍢𓍢ࣩ 🤩Главный кинн Герберта это . . . ㅤㅤㅤㅤ🥹🥹🥹@cyyybersaul! 🥹🥹 ㅤㅤㅤㅤㅤ @YesIkinnLCB | #MainKinn
custom 52062312888764043413custom 61455847973653117082
ㅤㅤㅤ🤩⪩ִ𓍢𓍢ࣩ 🤩Главный кинн Ишмаэль это . . . ㅤㅤㅤㅤㅤㅤ🥹🥹🥹@Glamkinn! 🥹🥹 ㅤㅤㅤㅤㅤ @YesIkinnLCB | #MainKinn
custom 62331015034149354273custom 62331565906654745722
ㅤㅤㅤ🤩⪩ִ𓍢𓍢ࣩ 🤩Главный кинн Кэтрин это . . . ㅤㅤㅤ🥹🥹🥹@psycholovesophy! 🥹🥹 ㅤㅤㅤㅤㅤ @YesIkinnLCB | #MainKinn
custom 52062312888764043415custom 62331565906654745724custom 62331015034149354273
ㅤㅤ🤩⪩ִ𓍢𓍢ࣩ 🤩Главный кинн Линтона это . . . ㅤㅤ🥹🥹🥹@MakuKaard_Kun ! 🥹🥹 ㅤㅤㅤㅤㅤ @YesIkinnLCB | #MainKinn
custom 52062312888764043413custom 62331565906654745723
( 🌟🌟 ) :: привет снова! хочу сообщить, что мы не принимаем в "Главный кинн *имя персонажа* это . . ." людей с длинным юзернеймом или же вовсе без него. первая причина почему мы не принимаем людей с длинным юзернеймом: он попросту не вмещается в наше оформление. вторая причина состоит на том, что нам нужен ваш ЮЗЕРНЕЙМ, чтобы вставить его как вашего главного кинна. об этом было написано мной, когда только провелся пер…
custom 52062312888764043415custom 62331015034149354273
ㅤㅤ🤩⪩ִ𓍢𓍢ࣩ 🤩Главный кинн Сичунь это . . . ㅤㅤㅤ🥹🥹🥹@En00_o ! 🥹🥹 ㅤㅤㅤㅤㅤ @YesIkinnLCB | #MainKinn
custom 61455847973653117084custom 62331565906654745723custom 52062312888764043412custom 62331015034149354271
ㅤㅤ🤩⪩ִ𓍢𓍢ࣩ 🤩Главный кинн Хитклиффа это . . . ㅤㅤㅤ🥹🥹🥹@IrlGasaiYuno! 🥹🥹 ㅤㅤㅤㅤㅤ @YesIkinnLCB | #MainKinn
custom 52062312888764043415custom 61455847973653117084👍1
ㅤㅤ🤩⪩ִ𓍢𓍢ࣩ 🤩Главный кинн Хитклиффа это . . . ㅤㅤㅤ🥹🥹🥹@Everyheathcliff! 🥹🥹 ㅤㅤㅤㅤㅤ @YesIkinnLCB | #MainKinn
custom 52062312888764043415custom 62331565906654745722
🤩 : Ещё пять ждем. 🎐 ( 🌟🌟 ) :: закрывай лавочку, все. 🤩 : Закрыл. 🤩
custom 52062312888764043414❤🔥3
🤩: хуярь. Разве мы делаем исключения? ( 🌟🌟 ) :: понял, сэр.
custom 52062312888764043414
Showing the 12 most recent of 20 posts we hold for @YesIkinnLCB. 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 — 448,689 of 1,336,469entries 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.
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.
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.
“Да, я кинню и я. . . [ Limbus Company! ]” (@YesIkinnLCB), 186 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/YesIkinnLCB.
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.