Channel
@n707ana
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
103subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001681276844 |
|---|---|
| Type | Channel |
| Username | @n707ana |
| Created | 11 July 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/n707ana |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 18:27 | 103 | -1 |
| 9 Aug 2026, 09:17 | 104 | no change |
| 7 Aug 2026, 19:55 | 104 | first reading |
10 posts held, back to 7 February 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 10 posts for this entry, the most recent from 8 March 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
444 reactions across 10 posts, in 10 distinct kinds. The most used accounts for 23.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5276463384374553960 | 104 | 23.4% | |
| custom 5278324466718353026 | 94 | 21.2% | |
| custom 5260465185247738844 | 89 | 20.0% | |
| custom 5202109215488882460 | 79 | 17.8% | |
| custom 5202030127961093570 | 35 | 7.88% | |
| custom 5346122355141784656 | 16 | 3.60% | |
| custom 5202202622437637257 | 12 | 2.70% | |
| custom 5201904117915600322 | 8 | 1.80% | |
| custom 5276366404013014503 | 6 | 1.35% | |
| custom 5307883372247266618 | 1 | 0.225% |
Custom emoji. Every row above is a 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 10 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 444reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 7 February 2024 to 8 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.
с 8 марта милые!!! извините, что совсем пропали пока нет сил и идей для постов😓 надеюсь вы хорошо провели этот день!! с праздником любимые наши🌟🌟
custom 527646338437455396025custom 526046518524773884415custom 52783244667183530268
Signed ㅤㅤㅤ ૮˃̵֊ ˂̵ ''たくみ
✦ Тест: кем из Наны вы были написаны... • ссылка #тесты
custom 520210921548888246017custom 526046518524773884411custom 52783244667183530266
Signed nana!🍓#сигма
всех с 14 февраля золотые!¡🥰 извиняемся за долгое отсутствие постов, совсем нет сил(( но обещаем, что в скором времени будем показываться почаще!🌟
custom 527832446671835302614custom 52021092154888824609custom 52764633843745539608
Signed bloodm1w
⟡ котята, вы спрашивали планируем ли мы создавать свои тгк! так воь; мы всё же решили не ждать 1к и уже создать и начать потихоньку их продвигать🍓 будем благодарны всем, кто подпишется и поддержит нас в нашем начинании! ✩࿐⋆* @s3x77pist3ls ~ 😩 ✩࿐⋆* @parak7ss ~ 😄
custom 526046518524773884416custom 52783244667183530268custom 52764633843745539605
Signed bloodm1w
здравствуйте, пока
custom 526046518524773884428custom 527832446671835302611custom 520203012796109357010custom 52764633843745539607custom 52021092154888824604
Signed гузель
спасипа родные за такое большое количество наналфагов¡! всех оче люблю ૮꒰ ˶• ༝ •˶꒱ა
custom 527832446671835302626custom 526046518524773884415custom 52021092154888824609custom 52764633843745539606custom 52020301279610935704
Signed bloodm1w
я вас люблю давайте встречаться
custom 527646338437455396033custom 527832446671835302616custom 520210921548888246015custom 52020301279610935702
Signed nana!🍓
ВЫ ТАКИЕ— планируете свои личные тгк создавать??? ⊹ планируем!!!!!! на 1000+ наналфагов сто проц буде
custom 520210921548888246022custom 53461223551417846569custom 52763664040130145036custom 52783244667183530263custom 52604651852477388442
Signed nana!🍓
Photo, posted without a caption
custom 527646338437455396020custom 520203012796109357012custom 53461223551417846567custom 52021092154888824603custom 52783244667183530262
Signed nana!🍓
хочуспатьᐡ⸝⸝⊃ ·̫ <⸝⸝ᐡ
custom 520220262243763725712custom 52019041179156003228custom 52020301279610935707custom 52604651852477388442custom 53078833722472666181
Signed bloodm1w
Showing the 10 most recent of 10 posts we hold for @n707ana. 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“n'anal” (@n707ana), 103 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/n707ana.
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.