Channel
@NAN1_SAMA
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Cite this entry
1,615subscribers
-13 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002781335696 |
|---|---|
| Type | Channel |
| Username | @NAN1_SAMA |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/NAN1_SAMA |
Art & design — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 78% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 02:01 | 1,615 | -7 |
| 13 Sept 2026, 19:37 | 1,622 | -1 |
| 10 Sept 2026, 07:21 | 1,623 | -4 |
| 4 Sept 2026, 19:18 | 1,627 | +1 |
| 1 Sept 2026, 06:12 | 1,626 | -2 |
| 26 Aug 2026, 18:43 | 1,628 | +1 |
| 23 Aug 2026, 11:03 | 1,627 | +2 |
| 20 Aug 2026, 08:03 | 1,625 | +3 |
| 17 Aug 2026, 12:55 | 1,622 | +1 |
| 14 Aug 2026, 00:17 | 1,621 | -4 |
| 10 Aug 2026, 09:04 | 1,625 | -3 |
| 9 Aug 2026, 10:17 | 1,628 | first reading |
19 posts held, back to 18 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 page of 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 19 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
3,205 reactions across 19 posts, in 5 distinct kinds. The most used accounts for 31.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5203927249375483529 | 1,010 | 31.5% | |
| custom 5445399669490330155 | 908 | 28.3% | |
| 💘 | 620 | 19.3% | |
| 💅 | 435 | 13.6% | |
| 🦄 | 232 | 7.24% |
Custom emoji. 2 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 are Telegram’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 19 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 3,205 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 18 July 2026 to 5 August 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @NAN1_SAMA. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 19 most recent posts we hold for this entry, published 18 July 2026 to 5 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
какой формат спидпеинта для вас наиболее удобный? (по времени)
The shares total 144%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
custom 544539966949033015533💅13💘8custom 52039272493754835297
отныне я это буду показывать всем новым знакомым, как интро/видео-знакомство/карточка для коммуникации
custom 520392724937548352991custom 544539966949033015526💘21
💕 У тебя новое сообщение! Наконец-то я закончила этот... шедевр кинематографа👍🥰👍🥰👍🥰 Мне было очень лень рисовать Юмико так что одежду подобрала наугад sorry ↩️ Свайпни для ответа.
custom 544539966949033015583custom 520392724937548352926💅19💘6
аригатошечки за заказ @devil00404 🍤
custom 5203927249375483529182custom 544539966949033015557💘40
всё гайсы, меня теперь не заставить рисовать по другой причине я полностью собрала компьютер примерно недельку назад, первым же делом скачала резик...уже полностью прошла resident evil village (хотя стоило по хорошему хотя бы начать с прошлой части) я очень довольна 😊
💘103💅37
Гифтик для наньки
custom 5203927249375483529100custom 544539966949033015532💅27💘9
мне кажется, я какую-то нирвану познала, когда у меня с первого раза начали получаться вещи, которые я до этого не рисовала никогда
custom 5203927249375483529185💅61🦄40💘11
у меня какой-то вайб ВКшных стикеров от этого арта
💅89🦄22💘4custom 52039272493754835292custom 54453996694903301552
аригатошечки за заказ @Soft_lolita 🌈
💘143💅44custom 520392724937548352929🦄7custom 54453996694903301551
Это так называемый кризис 20 лет?
custom 520392724937548352986🦄19custom 544539966949033015517💘5
когда смешно пошутил (туалетный юмор)
💘191💅43custom 520392724937548352927🦄4custom 54453996694903301554
хорошо, ценник пусть будет в 667 рублей, кидайте в комментарии свой любимый мем, я выберу тот, что понравится...ставки реальные, я надеюсь, никому эт не надо объяснять
custom 520392724937548352976🦄13custom 544539966949033015511
Showing the 12 most recent of 19 posts we hold for @NAN1_SAMA. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
какой формат спидпеинта для вас наиболее удобный? (по времени)
The shares total 144%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
как вы относитесь к платному контенту за звёзды? 💫
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 19 most recent posts we hold, published 18 July 2026 to 5 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 2 registered channels — 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“ʚ𝙣𝙖𝙣𝙞 𝙤𝙫𝙚𝙧𝙙𝙤𝙨𝙚ɞ” (@NAN1_SAMA), 1,615 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/NAN1_SAMA.
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.