Telegram RegisterThe public register of Telegram
Telegram profile photo for sana - chan ! archive

Channel

sana - chan ! archive

@twicesana_channn

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

95subscribers

-3 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1001949946359
TypeChannel
Username@twicesana_channn
Created15 July 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded10 August 2026
Last confirmed live12 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/twicesana_channn

Growth

959896.510 August 2026 — 98 subscribers10 August 2026 — 98 subscribers18 August 2026 — 96 subscribers26 August 2026 — 98 subscribers3 September 2026 — 96 subscribers12 September 2026 — 95 subscribers10 August 202612 September 2026
6 measurements spanning 33 days, net -3. 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 95–98 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 07:5695-1
3 Sept 2026, 17:1796-2
26 Aug 2026, 11:1398+2
18 Aug 2026, 15:0396-2
10 Aug 2026, 16:0598no change
10 Aug 2026, 03:4698first reading

Engagement

8 posts held, back to 6 July 2024the 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 8 posts for this entry, the most recent from 13 July 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

267 reactions across 8 posts, in 13 distinct kinds. The most used accounts for 44.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 545401777047785499411844.2%
6524.3%
💘3111.6%
🥰186.74%
💋72.62%
🔥62.25%
🕊62.25%
🍓51.87%
🤝41.50%
❤‍🔥31.12%
🤗20.749%
💔10.375%
😍10.375%

Custom emoji. One 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 count beside it is 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 8 of the 8 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 267 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

Recent posts

13 Jul 2024, 11:59 UTC≈3,460 views53 reactionsread 10 August 2026
Photo

они извинились перед саной, спасибо всем, кто распостранял! но всё равно мне не даёт это покоя, потому что они знают с какими людьми работают, и какая у них фанбаза, и соответственно должны понимать, что любой комментарий, даже случайный, может создать целую волну хейта в сторону их же амбассадоров. я очень сильно надеюсь, что теперь они будут следить на какие комментарии отвечают.

custom 5454017770477854994318💘7🤝4❤‍🔥3

13 Jul 2024, 11:33 UTC≈3,290 views33 reactionsread 10 August 2026
Photo

что касается ysl, так они пробили дно, отвечая сердечками на хейтерские комментарии в отношении саны в инстаграме. это отвратительный поступок, который требует огласки. поэтому, прошу распространить. Dear YSL, It comes to our attention that one of your admin shades Sana in the comment section, we are truly grateful that you chose Sana as the Japan Ambassador but we do not tolerate the disrespect action against her.

custom 5454017770477854994206🥰5💔1💘1

13 Jul 2024, 11:18 UTC≈2,080 views27 reactionsread 10 August 2026
Photo

сана в инстаграм! — я посетила поп-ап магазин 'ysl love shine factory' ! оформление магазина красивое и милое, не могу нарадоваться 🍬✨ здесь много всего классного, обязательно загляните 🩷

10custom 54540177704778549947💘5🔥2🤗2🥰1

13 Jul 2024, 11:15 UTC≈1,560 views23 reactionsread 10 August 2026
Photo

сана в инстаграм - стори! — уже завтра 🩵 ой, двенадцатое июля уже подошло к концу, получается, что уже сегодня. я полежала в ванной, немного отдохнула и сейчас упражняюсь с масочкой для лица. мне уже нужно ложиться спать. уансы, которые завтра придут к нам, тоже уже должны ложиться. спокойной ночи вам, насладитесь завтрашним днём!!! с нетерпением жду возможности услышать замечательные голоса уансов! ох, уже сег

💘11custom 545401777047785499454🥰2🕊1

10 Jul 2024, 11:56 UTC≈1,290 views42 reactionsread 10 August 2026
Photo

сана для прада, ты всегда будешь популярна

custom 54540177704778549941812💋5💘2🕊2🥰2😍1

9 Jul 2024, 15:01 UTC≈1,320 views19 reactionsread 10 August 2026

ПРЕМЬЕРА 'dive' ! 🪸

custom 545401777047785499495🥰3🍓1🕊1

6 Jul 2024, 08:37 UTC≈1,070 views37 reactionsread 10 August 2026
Photo

сана сменила аватарку в баббл!

custom 5454017770477854994215💘3🥰3🍓2🕊2🔥1

6 Jul 2024, 08:26 UTC981 views33 reactionsread 10 August 2026
Photo

сана в инстаграм! — смузи 'лунный свет'🥤🕛🥤🍓

15custom 54540177704778549947🔥3🍓2💋2💘2🥰2

Showing the 8 most recent of 8 posts we hold for @twicesana_channn. 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.

Forward network

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.

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

“sana - chan ! archive” (@twicesana_channn), 95 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/twicesana_channn.

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.