Channel
@nass_ttv
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,704subscribers
-13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001638960751 |
|---|---|
| Type | Channel |
| Username | @nass_ttv |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/nass_ttv |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 23:47 | 2,704 | -4 |
| 25 Aug 2026, 20:55 | 2,708 | -3 |
| 19 Aug 2026, 22:22 | 2,711 | -3 |
| 13 Aug 2026, 13:05 | 2,714 | -2 |
| 10 Aug 2026, 03:57 | 2,716 | -1 |
| 7 Aug 2026, 09:31 | 2,717 | no change |
| 7 Aug 2026, 09:26 | 2,717 | first reading |
5 posts held, back to 10 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 2 pagesof 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 5 posts for this entry, the most recent from 3 July 2026. An engagement rate over an empty window would be a number about nothing.
87 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 44.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5431879760982606301 | 39 | 44.8% | |
| custom 5438365582506366885 | 22 | 25.3% | |
| custom 5438584926486180741 | 13 | 14.9% | |
| custom 5445106748425811027 | 9 | 10.3% | |
| ❤🔥 | 4 | 4.60% |
Custom emoji. 4 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 5 of the 5 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 87reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 10 June 2026 to 3 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.
літо — це не тільки про фото з морозивом, а й про деталі ⭐️ ці фони з текстурою морозива додадуть легкості будь-якому дизайну. вони чудово підійдуть для сторіс, обкладинок, постів, добірок або просто як ніжний акцент у вашому контенті. зберігайте собі та використовуйте, коли захочеться додати трішки смаку⭐️ Inspiothèque
custom 543187976098260630111custom 54451067484258110272
трішки повсякденних стікерів⭐️ більше шукайте в коментарях, і також пишіть тему на яку ви хочете побачити стікери збірка різних написів⭐️ #стікери забустити канал Inspiothèque
custom 54385849264861807419❤🔥4custom 54318797609826063012
⭐️палітра теплого літнього ранку поєднання м’якого рожевого грейпфрута та вершково-жовтого створює відчуття затишку, легкості й безтурботності ідеально для жіночних блогів, lifestyle-контенту, beauty, self-care, романтичної естетики та теплих особистих історій⭐️ Inspiothèque
custom 543187976098260630110custom 54451067484258110277custom 54383655825063668853
нова порція стікерів⭐️ мікс із вінтажних деталей, написів, милих дрібничок та елементів, які легко впишуться у ваші сторіс та пости⭐️ більше стікерів знайдете у коментарях #стікери Inspiothèque
custom 543836558250636688515custom 54318797609826063016custom 54385849264861807413
🍃 cottagecore — естетика, яка вже давно вийшла за межі Pinterest вона про спокій, простоту та любов до дрібниць. Польові квіти, вінтажні деталі, домашня випічка, книги, мереживо та життя без поспіху 🌾 у дизайні та оформленні контенту cottagecore впізнати легко: 🤩 м’які природні кольори 🤩 рукописні та вінтажні шрифти 🤩 квіткові елементи й ілюстрації 🤩 легка “сільська” атмосфера 🤩 відчуття затишку та тепла ця естети…
custom 543187976098260630110custom 54383655825063668854custom 54385849264861807411
Showing the 5 most recent of 5 posts we hold for @nass_ttv. 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 — 1,073,881 of 1,624,904entries 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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“Inspiothèque • все про і для ведення блогу nass.ttv” (@nass_ttv), 2,704 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/nass_ttv.
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.