Telegram RegisterThe public register of Telegram
Telegram profile photo for Amaii cos ^_^

Channel

Amaii cos ^_^

@amaiishinsen

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

142subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002165292643
TypeChannel
Username@amaiishinsen
Descriptionпривееетик!! Я Амаи, и на этом канале ты можешь следить за моей жизнью, косплей творчеством и рисуночками!! Лс- @amaiicos #iloveeveryone
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/amaiishinsen

Growth

1427 August 2026 — 142 subscribers8 August 2026 — 142 subscribers7 August 20268 August 2026
2 measurements spanning 2 days. 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 141–143 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 22:00142no change
7 Aug 2026, 06:02142first reading

Engagement

16 posts held, back to 16 February 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
39.4%
avg views ÷ 142 subscribers
Avg views / post
56.0
1 post measured
Reaction rate
3.57%
reactions ÷ views · ER floor
Posts in window
1
of 16 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 29 July 2026
Posts held16 (16 February 202629 July 2026)
Views total56
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 22:00 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.

What this channel posts

Photos
276
Videos
38
Links
31

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
12s
Average length
12s

Measured directly from 1 video 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.

Reaction mix

262 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 39.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 535523171878360669410339.3%
custom 54473162556965058337428.2%
custom 53436897286150033827227.5%
custom 534404322589830006972.67%
41.53%
custom 534352232367470759920.763%

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

Measured over the 16 most recent posts we hold, published 16 February 2026 to 29 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.

Telegram Stars

Stars received
63
across the posts below
Posts paid on
3
of 16 we hold a reading for · 19%
Most on one post
49
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @amaiishinsen. 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 16 most recent posts we hold for this entry, published 16 February 2026 to 29 July 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.

Recent posts

29 Jul 2026, 12:33 UTC56 views2 reactionsread 8 August 2026

Частичный переезд?... 🤩🤩🤩🤩🤩🤩🤩🤩 В этом тгк буду появляться куда чаще!! 🐹 чмоки-чмок

2

5 Apr 2026, 14:42 UTC230 views11 reactionsread 8 August 2026
Forwarded from @ACHRainbowVideo

#щп #эму

custom 54473162556965058335custom 535523171878360669442

28 Mar 2026, 09:38 UTC278 views20 reactionsread 8 August 2026

Доброго дня!! Сегодня буду в Хонами на кице с 14 до 16 📻

custom 535523171878360669410custom 53436897286150033826custom 54473162556965058334

24 Mar 2026, 12:06 UTC255 views17 reactionsread 8 August 2026
Photo

Бтввв, вот вам порисулька с анхане 🌟 #рисункиамаи

custom 53436897286150033826custom 53552317187836066946custom 54473162556965058335

24 Mar 2026, 10:59 UTC223 views19 reactionsread 8 August 2026
Photo

✍️✍️✍️✍️🍊

custom 534368972861500338210custom 53552317187836066945custom 53440432258983000694

21 Mar 2026, 12:18 UTC162 views8 reactionsread 8 August 2026

Давайте попробуем 50 реактов, а я вам допы 💤

custom 53552317187836066946custom 53436897286150033821custom 53440432258983000691

20 Mar 2026, 20:15 UTC378 views54 reactions1 Starread 8 August 2026
Photo

🌟 🎀агамине 🎀ин 🌟 ➿➿➿➿ 🔤 не могу не улыбаться когда вижу, как улыбается кто-то другой!! 🤩 ➿➿➿➿ Рт/реакты пожалуйста💤

custom 535523171878360669422custom 544731625569650583316custom 534368972861500338215custom 53440432258983000691

9 Mar 2026, 05:20 UTC181 views14 reactions49 Starsread 8 August 2026
Photo

Блииин, 8 марта так быстро пролетело, я всё забыла.. С прошедшим вас, милые дамы!!

custom 53552317187836066949custom 53436897286150033823custom 54473162556965058332

5 Mar 2026, 17:58 UTC186 views25 reactionsread 8 August 2026

На 8 марта постараюсь устроить вам сюрприз📻

custom 544731625569650583311custom 53552317187836066948custom 53436897286150033825custom 53440432258983000691

2 Mar 2026, 15:24 UTC226 views22 reactionsread 8 August 2026
Photo

🔤 🔤🔤🔤🔤 🔤🔤🔤🔤🔤🔤🔤🔤, моя милая Кохане 🐹 Жди ещё кучу мерча, костюмов и рисунков, лучший секайчик моц.. Все ивенты, карты и песни вбс безумно меня вдохновляют и дают мотивацию идти дальше. Моя цель- добиться таких же успехов, как этот сладкий хомячок 📻  🔤🔤🔤🔤🔤

custom 535523171878360669410custom 54473162556965058337custom 53436897286150033825

1 Mar 2026, 15:05 UTC187 views8 reactionsread 8 August 2026

Мы выступили кароче!! 😗 Если вкратце: ботинок прилетел в жюри, я опоздала на дефиле из-за булки, расплакалась, И МЫ ЗАНЯЛИ ТРЕТЬЕ МЕСТО🐹 Спасибо каждому кто был на лабубе, все милааашки 🎧🐹 Чмоки в обе щеки, скоро скину дефиле, увидимся!!

custom 53552317187836066944custom 53436897286150033822custom 54473162556965058332

1 Mar 2026, 07:55 UTC203 views17 reactionsread 8 August 2026
Photo

Едеммм ужн 😉😉😉

custom 54473162556965058337custom 53552317187836066946custom 53436897286150033824

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

Citation-graph rank

Citation-graph rank — 568,348 of 1,481,243entries 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

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

“Amaii cos ^_^” (@amaiishinsen), 142 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/amaiishinsen.

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.