Channel
@tsukerk
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
159subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002061257937 |
|---|---|
| Type | Channel |
| Username | @tsukerk |
| Description | Не забудьте взять мишку в постель и посмотреть под кровать лс: @tsukerka78 тт: tsukerka_kawaii |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/tsukerk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 17:31 | 159 | no change |
| 8 Aug 2026, 13:00 | 159 | first reading |
11 posts held, back to 16 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. It is computed over the 8 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 July 2026 |
|---|---|
| Posts held | 11 (16 July 2026 – 30 July 2026) |
| Views total | 751 |
| Reactions total | 81 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 17:31 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.
Lifetime counters from Telegram’s own channel header, read 8 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 2 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.
102 reactions across 10 posts, in 12 distinct kinds. The most used accounts for 23.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5411149306759507196 | 24 | 23.5% | |
| custom 5300774355263848708 | 12 | 11.8% | |
| custom 5474429027026504220 | 12 | 11.8% | |
| 🥰 | 10 | 9.80% | |
| custom 5832271326873656894 | 9 | 8.82% | |
| custom 5206212665898201010 | 8 | 7.84% | |
| custom 5310273306799132614 | 7 | 6.86% | |
| custom 5244831298131866287 | 6 | 5.88% | |
| ❤ | 5 | 4.90% | |
| custom 5327840629277884816 | 4 | 3.92% | |
| 😎 | 4 | 3.92% | |
| 👍 | 1 | 0.98% |
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 10 of the 11 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 102reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 16 July 2026 to 30 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.
мне ещё приехали штучки на новые косплеи, так что будет много всего, а то уже так то июль заканчивается ...✨
👍1🥰1😎1custom 53102733067991326141custom 53278406292778848161custom 58322713268736568941
Signed 𝚃𝚂𝚄𝚁𝙸 ౨ৎ
🤩🤩✨✨✨✨🤩🤩 🤩 оп, опять алнст !☕️ 🤩я только этой ночью сделала Луку и мне уже опять хочется его сделать ещё раз, только получше, мне не оч нравится ☕️ но что есть, то есть !
custom 52062126658982010108custom 53102733067991326143custom 53278406292778848163🥰1😎1
Signed 𝚃𝚂𝚄𝚁𝙸 ౨ৎ
много новой подписоты, так что непринуждённо напомню про свой щп канал, вдруг кому то будет интересно 🎸
🥰3custom 52448312981318662873custom 58322713268736568942
Signed 𝚃𝚂𝚄𝚁𝙸 ౨ৎ
🤩➡️✨🤩🤩🤩🤩🤩✨⬅️ 💋по базе закину фотки без обработки, потому что очень нравится 💋 спасибо за рт, реакты и подписки 🥰
custom 54111493067595071966🥰4custom 53007743552638487084custom 54744290270265042202
Signed 𝚃𝚂𝚄𝚁𝙸 ౨ৎ
🤩🤩🤩🤩🤩➡️💗💗💗💗💗🐻 🤩🤩😀😀😀😀😀😀😀😀 🌟🤩terranova! so far away !🤩🌟 🌟🤩🤩terranova! so far away !🌟 🌟🤩terranova! so far away !🤩🌟 она в проблематик эдите rt, reaction, comments, sweet kiss?~🤩 #Цукеркосп
custom 547442902702650422010custom 53007743552638487088custom 54111493067595071967🥰1
Signed 𝚃𝚂𝚄𝚁𝙸 ౨ৎ
✨✨✨🥰✨✨ ✨✨✨🥰✨ 🤩➖➖➖➖➖➖➖➖🤩 🤍🤍 🎠Косплей на Старр Нову, но это винтажный японский плакат/ обложка журнала✨ 🎠 🤍🤍 #valkyriecos
custom 52448312981318662871custom 54111493067595071961custom 58322713268736568941
Signed 𝚃𝚂𝚄𝚁𝙸 ౨ৎ
🌹 😡😢😠😟 😠🤯🥳😡🤬😱 🎀 ❤️🌟 🎀 🌟🌸😠🤬😟😳😟🥺, we can’t both exist. i’m going to become half of 😶😢🤯.. and i need 😶😢🤯 to know. that every moment you love being yourself .. that’s me loving 😶😢🤯 .🤩 😀😀😀😀😀😀😀😀 рт, реакции ?? #косплей
Signed 𝚃𝚂𝚄𝚁𝙸 ౨ৎ
𐔌 ׅ 🌹✧ arima kana 𐙚 🌹ׅ ֹ ˆ 𖦹. ݁₊ * ᡣ𐭩︵ ࿔𐦍↺ ੈ✩‧₊˚*ྀི ִ ⊹ ۫ ꒰ ♪ ꒱꒱ ─꯭─ 𓏵 ─꯭─ ꒰꒰ ♪ ꒱ ִ⊹ ◟ OSHINOKO🌱 ₎ ┈ ⇅x ⟩ ──── ⭒𖹭 ﹪🍓 𓇻 ᯾ ⋮ 𝖼𝖿 — #CUTE!!᯾ ᨶ႒ᩚ ─ જ⁀➴ ♡ → ⋮🍰 мью/рт/реакции 🍓
custom 58322713268736568941
Signed 𝚃𝚂𝚄𝚁𝙸 ౨ৎ
..°ꞌꞋ ࣪ 𝓷𝓪𝔃𝓾𝓷𝓪 𝓷𝓲𝓽𝓸 . ๋࣭ .ೃ࿔.𖥔 ݁..° • ꞌꞋ//𝓮𝓷𝓼𝓮𝓶𝓫𝓵𝓮 𝓼𝓽𝓪𝓻𝓼 //๋࣭ . “ - "𝓘𝓯 𝓼𝓸𝓶𝓮𝓽𝓱𝓲𝓷𝓰 𝓲𝓼 𝓫𝓸𝓽𝓱𝓮𝓻𝓲𝓷𝓰 𝔂𝓸𝓾, 𝓳𝓾𝓼𝓽 𝓽𝓮𝓵𝓵 𝔂𝓸𝓾𝓻 𝓫𝓲𝓰 𝓫𝓻𝓸𝓽𝓱𝓮𝓻 𝓪𝓫𝓸𝓾𝓽 𝓲𝓽." ꞌꞋ ࣪･⁷ .࣪･ﾟ ₊˚ ⁺ ⋆ . .࿐‧ ₊˚ . ⁺. ꞌꞋ ࣪• #cos #enstars·˚ ༘
custom 54111493067595071963custom 52448312981318662871custom 58322713268736568941
Signed 𝚃𝚂𝚄𝚁𝙸 ౨ৎ
буду делать пост в Лейлу и заказывать новый косплей (может даже не один🤩) , так что отсыпаюсь и начинаю работать снова 🌟
❤4custom 53102733067991326142custom 52448312981318662871
Signed 𝚃𝚂𝚄𝚁𝙸 ౨ৎ
💥💥💥💥💥💥💥💥💥💥 🥱чучуть пропала, никак не могу набраться сил после дня рождения ... ✨ у меня не так много фоток с дня рождения, зато вчера были в красивом чайна ресторанчике, было ооочень вайбульно ❤️ + подаруночки от сис (и маленькеме ивти от подруги), супер няшный новый итабэг, буду оформлять и вам хвастаться ⭐️
custom 54111493067595071967custom 58322713268736568943😎2❤1custom 53102733067991326141
Signed 𝚃𝚂𝚄𝚁𝙸 ౨ৎ
Showing the 11 most recent of 11 posts we hold for @tsukerk. 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 — 770,528 of 1,480,975entries 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 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.
Named by
Channels on the register whose posts name this channel's handle.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“° 『D』ąıƖყ 『T』ʂųrıı °” (@tsukerk), 159 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/tsukerk.
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.