Telegram RegisterThe public register of Telegram
Telegram profile photo for ANAMI

Channel

ANAMI

@anami_cos

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

34subscribers

+1 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002730315503
TypeChannel
Username@anami_cos
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live1 September 2026
Measurements held3
Confirmed unchanged3 times, most recently 1 September 2026
On Telegramt.me/anami_cos

Growth

333433.59 August 2026 — 33 subscribers11 August 2026 — 33 subscribers17 August 2026 — 34 subscribers9 August 202617 August 2026
3 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 33–34 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 16:0734+1
11 Aug 2026, 01:4533no change
9 Aug 2026, 12:3133first reading

Engagement

10 posts held, back to 16 April 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 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 10 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
15s
Average length
8s

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.

Reaction mix

83 reactions across 10 posts, in 11 distinct kinds. The most used accounts for 32.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 58885153924935902202732.5%
custom 53575799534979838891416.9%
custom 58908886067377670281416.9%
custom 535070203581983398989.64%
custom 523140197477937217078.43%
custom 534385280422827995578.43%
custom 594079229560645617422.41%
custom 544308049452467999711.20%
custom 588847060027966129411.20%
custom 589105211184775762311.20%
custom 589125568900262151011.20%

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

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

Recent posts

20 Jul 2026, 06:59 UTC133 views14 reactionsread 11 August 2026
Photo

Итаааак Вот и подъехал отзыв на мой четвёртый Аникон 🦊🦊🦊 В пятницу в косплее циркового Сиэля из Тёмного Дворецкого, в субботу Леди Сиэль. Была очень рада со всеми пообщаться и пофотографироваться🌟 Отдельно хочу сказать спасибо участнице, которая пела песню из Наны. Я прям прослезилась, ностальгия в глаз попала💔 это было прекрасно! Ребята из гранда "магистр дьявольского культа, восточный аул" завоевал моё сердечко.

custom 58885153924935902207custom 53438528042282799554custom 58908886067377670283

19 Jul 2026, 05:40 UTC26 views10 reactionsread 11 August 2026
Photo

Что стабильно из года в год? Вижу Махито - фотографируюсь с Махито❤️ #Anicon, #СПб, день 2

custom 52314019747793721705custom 58885153924935902203custom 53438528042282799552

17 Jul 2026, 12:28 UTC24 views5 reactionsread 11 August 2026
Video message

Video message, posted without a caption

custom 52314019747793721702custom 58885153924935902202custom 54430804945246799971

29 Jun 2026, 14:45 UTC37 views7 reactionsread 11 August 2026
Forwarded from @sbnpenVideo

танцульки💃🍑 пик имир энни леви саша эрен

custom 58885153924935902202custom 58908886067377670282custom 59407922956064561742custom 53438528042282799551

13 Jun 2026, 16:20 UTC50 views5 reactionsread 11 August 2026
Forwarded from @reymi_17Photo

Ну что, tatakae? ⚔️ Вот и закончился большой фото-проект, который я планировал почти год. Это мой первый опыт, так что будет многобукв, терпите. Не всё пошло по плану в подготовке, из-за некоторых обстоятельств мне пришлось реветь кровью в дедлайне по крафту УПМ, но сам процесс - тайминги на 12 персонажей, сбор локации, ведение съёмки и тд - мне безумно понравился. Не без косяков, но я многому научился сам и многом

custom 53507020358198339893custom 58884706002796612941custom 58885153924935902201

13 Jun 2026, 14:05 UTC302 views10 reactionsread 11 August 2026
Photo

"ГДЕ МОЁ ТИТАНЬЁ?!" (с) Имир

custom 53575799534979838895custom 58885153924935902204custom 58908886067377670281

13 Jun 2026, 09:10 UTC60 views9 reactionsread 11 August 2026
Video

На повестке дня мадам Леонхарт⚔️😐 #attackontitan

custom 53575799534979838894custom 58885153924935902203custom 58908886067377670282

25 Apr 2026, 14:28 UTC76 views10 reactionsread 11 August 2026
Photo

Ходят легенды, что уже скоро стартует набор заявок на питерский Anicon. И я уже в предвкушении, что же придумать на этот раз🌟 Задумочка есть, осталось доработать детали

custom 53507020358198339895custom 53575799534979838893custom 58908886067377670282

16 Apr 2026, 15:32 UTC77 views5 reactionsread 11 August 2026
Photo

Тут я радуюсь подарочкам от Клюкво Надпись на футболке в самое сердечко❤️

custom 58908886067377670283custom 58910521118477576231custom 58912556890026215101

16 Apr 2026, 13:31 UTC69 views8 reactionsread 11 August 2026
Photo

Запоздало продолжаю выкладывать фоточки с феста🫥 Как же классно встречать знакомых даже находясь в другом городе🫶

custom 58885153924935902205custom 53575799534979838892custom 58908886067377670281

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

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

“ANAMI” (@anami_cos), 34 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/anami_cos.

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.