Telegram RegisterThe public register of Telegram
Telegram profile photo for ◌Нанами 🪷 • ┈┈ ◌ ··· ⋅·· ◌

Channel

◌Нанами 🪷 • ┈┈ ◌ ··· ⋅·· ◌

@yumiartik

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

600subscribers

-1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002399068266
TypeChannel
Username@yumiartik
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/yumiartik

Growth

6006026016 August 2026 — 601 subscribers6 August 2026 — 601 subscribers7 August 2026 — 602 subscribers14 August 2026 — 600 subscribers6 August 202614 August 2026
4 measurements spanning 8 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 600–602 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 13:58600-2
7 Aug 2026, 02:24602+1
6 Aug 2026, 17:48601no change
6 Aug 2026, 11:04601first reading

Engagement

13 posts held, back to 13 July 2026the 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 · 30 days
41.5%
avg views ÷ 600 subscribers
Avg views / post
249
5 posts measured
Reaction rate
13.7%
reactions ÷ views · ER floor
Posts in window
5
of 13 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held13 (13 July 20266 August 2026)
Views total1,245
Reactions total171
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 17:48 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.

Reaction mix

343 reactions across 13 posts, in 13 distinct kinds. The most used accounts for 25.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54404187014278944498725.4%
custom 54385603120285886908625.1%
7221.0%
custom 5467401820580115361195.54%
🔥185.25%
🥰154.37%
👾144.08%
custom 5346128853427321899123.50%
❤‍🔥61.75%
custom 541358452744654152951.46%
🍓51.46%
custom 534378354788063336320.583%
💘20.583%

Custom emoji. 6 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 13 of the 13 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 343reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 13 July 2026 to 6 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.

Recent posts

6 Aug 2026, 13:52 UTC70 views17 reactionsread 6 August 2026
Forwarded from @sweet_wave0Photo

пытаюсь в перспективу, вахуи что за несколько часов отрисовала это🙏

custom 54404187014278944499custom 54385603120285886904custom 53461288534273218993custom 54135845274465415291

5 Aug 2026, 11:00 UTC368 views68 reactionsread 6 August 2026
Photo

Наконец-то закончила!! 🤍 Как думаете было бы Ксено легче во время работы, если бы они с Сенку были коллегами? Как по мне ему всё время просто не хватало поддержки со стороны друзей или учёных Буду очень рада активности :З

custom 54404187014278944492919🔥15❤‍🔥2💘1custom 54135845274465415291custom 54385603120285886901

31 Jul 2026, 18:16 UTC241 views17 reactionsread 6 August 2026

Ребят вы бы заказали коммишки, если бы я сделала скидку 30-40%? У меня есть некоторые нужды, но заказов нет так что интересно есть желающие или нет 💐

👾13custom 53437835478806333632custom 54674018205801153612

31 Jul 2026, 18:14 UTC227 views49 reactionsread 6 August 2026
Photo

Спойлер к арту! <3 Вообще у меня щас не самый хороший этап в жизни, поэтому стала так редко рисовать. Очень плохо из-за тревожных мыслей, жары, и проблем с некоторыми людьми. Так что ещё раз извиняюсь, что не активна тут. Ну и не могу не писать о том, что немного расстраивает актив тут.. комменты пишут 1-2 человека которым я ОЧЕНЬ благодаря за активность и хорошие слова!! А так хотелось бы чуть более активной аудит

custom 543856031202858869027custom 546740182058011536111custom 53461288534273218997custom 54135845274465415292👾1custom 54404187014278944491

23 Jul 2026, 09:32 UTC339 views20 reactionsread 6 August 2026

Кстати извиняюсь, что долго нет артов я была занята. Но скоро будет коммишка, и арт с Ксено

14custom 54674018205801153616

16 Jul 2026, 17:02 UTC676 views59 reactionsread 6 August 2026
Photo

Спойлер разворота!! #NanamiFamilyZINE

custom 544041870142789444936custom 543856031202858869013🥰7🔥3

16 Jul 2026, 13:44 UTC469 views6 reactionsread 6 August 2026

Сегодня ещё выложу спойлер к этому зину

🍓5custom 54135845274465415291

16 Jul 2026, 13:42 UTC450 views35 reactionsread 6 August 2026
Photo

🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 И опять коммиш для Yoshii!!

21custom 543856031202858869010custom 54404187014278944493🥰1

14 Jul 2026, 20:13 UTCviews —12 reactionsread 6 August 2026

Posted without readable text

custom 54385603120285886908❤‍🔥2custom 53461288534273218992

14 Jul 2026, 18:43 UTC418 views12 reactionsread 6 August 2026

Люблю этот день за то, что можно познакомиться с хорошими художниками!! Можете тут покидать свои арты, даже если у вас нет тгк, было бы интересно глянуть какие талантливые люди подписаны на меня 🫶

7custom 54404187014278944493custom 54385603120285886902

14 Jul 2026, 06:11 UTC≈1,480 views34 reactionsread 6 August 2026
Photo

Буду очень благодарна репостам!!💐 #PortfolioDay

custom 54385603120285886901610🥰7💘1

Showing the 12 most recent of 13 posts we hold for @yumiartik. 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

Citation-graph rank — 80,930 of 1,548,671entries 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.

Forward network

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.

Mentions

Named by 9 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.

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.

Cite this entry

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“◌Нанами 🪷 • ┈┈ ◌ ··· ⋅·· ◌” (@yumiartik), 600 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/yumiartik.

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.