Лен и Мия после событий музыкального проклятия Попробуете угадать что за момент?
💘16custom 52626112000169292397
Signed .exeBurosu♡病み

Channel
@nanakod
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
98subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001996818646 |
|---|---|
| Type | Channel |
| Username | @nanakod |
| Description | Проекты: Softiko, Musical Curse 𐔌 Находятся на этапе разработки 𐦯 Предложка: @NaNakOd_bot ЛС С0ЗД4Т3ЛЯ: @mikiurkak Ваши фан арты: @softikoarts |
| Created | Between 1 October 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/nanakod |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 11:32 | 98 | no change |
| 8 Aug 2026, 09:04 | 98 | first reading |
9 posts held, back to 2 June 2025 — 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 9 posts for this entry, the most recent from 31 October 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
209 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 41.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5262611200016929239 | 86 | 41.1% | |
| 💘 | 75 | 35.9% | |
| 🍓 | 31 | 14.8% | |
| custom 5330476609621219986 | 9 | 4.31% | |
| custom 5427042798878610107 | 8 | 3.83% |
Custom emoji. 3 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 9 of the 9 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 209reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 2 June 2025 to 31 October 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.
Лен и Мия после событий музыкального проклятия Попробуете угадать что за момент?
💘16custom 52626112000169292397
Signed .exeBurosu♡病み
- Все будет хорошо, моя дорогая Нилу.. Парные аватарки для подписчиков нашего тгк хех
custom 526261120001692923919💘8
Signed .exeBurosu♡病み
Тут есть фанаты Фости?
custom 526261120001692923913💘10
Signed .exeBurosu♡病み
Рады представить вам нового члена команды нанакод - Риша! Риша главный сценарист проекта «музыкальное проклятие» Под ее руководством скоро мы предоставим новые релизы к играм! art by -> @b3330_0
💘14custom 52626112000169292399
Signed .exeBurosu♡病み
⚠️ На пешеходном переходе замечена группа невменяемых сталкерш. Вызывающе-одетые двенадцатиклассницы из академии для девочек поздно вечером гуляют по городу. Очевидцы удтверждают, что они явно не в себе. Будьте бдительны! Берегите себя и близких!
💘15custom 52626112000169292394
Signed .exeBurosu♡病み
Всем привет, извиняемся за столь большие отклады планов, у нас были 3 кратные форс мажоры, но сейчас опять в работе!
custom 526261120001692923916💘8
Signed .exeBurosu♡病み
🎀:🎀🎀𐔌 ⋆.˚ʚ 💗 ɞ˚.⋆ ꒱🎀🎀:🎀 Спасибки рише, ходите - ищите Манна на wplace ^_^ / поняле ?¿ Где-то на юго-западе Москвы . . . 🎀:🎀🎀🎀🎀🎀🎀🎀🎀🎀:🎀
custom 52626112000169292399🍓5💘4
Signed ₊ · ? cᴀɯо_0
Soon…
🍓10custom 52626112000169292399
Signed .exeBurosu♡病み
⋆ ࣭ 🏳️🌈⭑. ๋ ࣭ PRIDE MONTH ! ๋ ࣭ ⭑🏳️🌈⋆ ࣭ ✨ Поздравляем всех с месяцем гордости, а также с окончанием учебного года \(^ 3 ^)/ ✨✨
🍓16custom 53304766096212199869custom 54270427988786101078
Signed .exeBurosu♡病み
Showing the 9 most recent of 9 posts we hold for @nanakod. 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 — 856,463 of 1,340,412entries 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.
@nanakod named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“NaNakOd TEAM 彡” (@nanakod), 98 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/nanakod.
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.