Telegram RegisterThe public register of Telegram
Telegram profile photo for момока (няшева)

Channel

момока (няшева)

@momokacos

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

111subscribers

+6 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-1002278177962
TypeChannel
Username@momokacos
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live15 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/momokacos

Growth

1031111077 August 2026 — 105 subscribers7 August 2026 — 104 subscribers9 August 2026 — 104 subscribers14 August 2026 — 103 subscribers28 August 2026 — 106 subscribers7 September 2026 — 104 subscribers15 September 2026 — 111 subscribers7 August 202615 September 2026
7 measurements spanning 39 days, net +6. 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 102–112 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 11:59111+7
7 Sept 2026, 01:56104-2
28 Aug 2026, 12:56106+3
14 Aug 2026, 11:23103-1
9 Aug 2026, 09:17104no change
7 Aug 2026, 18:47104-1
7 Aug 2026, 02:46105first reading

Engagement

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

What this channel posts

Video runtime
14s
Average length
14s

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

165 reactions across 13 posts, in 9 distinct kinds. The most used accounts for 27.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52648355077449550344627.9%
custom 52807098528998557253118.8%
❤3018.2%
custom 52898623895529191542112.7%
custom 52649318052066993162012.1%
❤‍🔥53.03%
💋53.03%
🥰53.03%
🍓21.21%

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

Measured over the 15 most recent posts we hold, published 31 July 2026 to 8 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

8 Aug 2026, 22:33 UTC26 views7 reactionsread 9 August 2026
Video

Знали бы вы, как я люблю это видео😔 Я его уже сюда выставляла, но хочу выставить ещё раз🥹 Хочу заказать какой-нибудь костюм на Эну, потому что я уж слишком её люблю. Как думаете, какой костюм мне заказать? Кидайте свои варианты!🤩

custom 52898623895529191543custom 52648355077449550342custom 52807098528998557252

Signed tashia chan ´ω`

7 Aug 2026, 21:35 UTC20 views2 reactionsread 9 August 2026
Forwarded from @mitacosPhoto

Lvl up! My birthday! вот стукнуло 8 августа , а это значит , что мне уже исполнилось 13 лет! Я очень рада , что создала этот канал и вообще в принципе пришла в косплей! Хочу сказать всем огромное спасибо а в особенности девчонкам GLR , Юки , мамбл и суглинку! За то что вы всегда были рядом!!! Я очень рада , что вы есть! Я очень рада тому чего успела добиться за этот год: Начать выступать на фестивалях Выйграть …

🍓1custom 52648355077449550341

Signed tashia chan ´ω`

7 Aug 2026, 11:41 UTC41 views9 reactionsread 9 August 2026

А подписчики из щп уже в курсе о новом косплее, который я заказала! Скорее подписывайся 🤩

❤4custom 52648355077449550342custom 52807098528998557252💋1

Signed tashia chan ´ω`

6 Aug 2026, 10:15 UTC24 views8 reactionsread 9 August 2026
Forwarded from @whatevericaaaanPhoto

🤩🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩 🩹 🌟 🩹 ˚ ༘ ⋆。˚ 🫗 ˚ ༘ ⋆。˚ 🫗 ˚ ༘ ⋆。˚ 🫗 - Я так рада, что все заботятся о своих друзьях...! Хехехе, все мы равны, когда болеем🩹 ⇢ ˗ˏˋ 🫗 ࿐ྂ ⇢ ˗ˏˋ 🫗 ࿐ྂ ⇢ ˗ˏˋ 🫗 ࿐ྂ 🩹 ❤️‍🔥 🩹 Ph

custom 52648355077449550343custom 52807098528998557252custom 52898623895529191542💋1

Signed tashia chan ´ω`

5 Aug 2026, 19:07 UTC54 views13 reactionsread 9 August 2026

Так же! Решилась обзавестись щп каналом. А то у многих он есть, а у одной меня нет🤩 https://t.me/+o_uBNjc5lzs2MDcy Так что заходите, присоединяйтесь🙏

custom 52648355077449550345custom 52807098528998557253❤2💋1custom 52649318052066993161custom 52898623895529191541

Signed tashia chan ´ω`

5 Aug 2026, 19:01 UTC50 views13 reactionsread 9 August 2026

Давайте так: Кто мне больше всего пойдёт из Бикомачи? (помимо Мем Чо, ахах) Кана😀 или Руби?😏 ..Или может быть Ай?🙂

❤5🥰3custom 52807098528998557253custom 52648355077449550341custom 52898623895529191541

Signed tashia chan ´ω`

4 Aug 2026, 23:11 UTC57 views17 reactionsread 9 August 2026

Всем огромное спасибо за поздравления! Я вас всех очень сильно люблю😭 Скоро ждите новый косплейчик! Она уже почти приехала ко мне 🤩

custom 52648355077449550348custom 52807098528998557253custom 52898623895529191543❤1🍓1🥰1

Signed tashia chan ´ω`

3 Aug 2026, 21:02 UTC446 views32 reactionsread 9 August 2026
Photo

Сегодня 4 августа, а значит наступил мой день рождения, и мне исполнилось 👀👀 лет🤩 За этот год много, что случилось, и я надеюсь, что дальше будет только лучше. Спасибо всем, кто был рядом. Надеюсь, что меня и дальше будут окружать надёжные и добрые люди как и в жизни, так и в косплей комьюнити. Знайте, я всех очень сильно люблю Ожидайте много новых образов, новых выступлений как и вместе с трио GLR и дуэтах, так и …

❤14custom 52649318052066993169custom 52807098528998557258custom 52898623895529191541

Signed tashia chan ´ω`

2 Aug 2026, 16:07 UTC100 views4 reactionsread 9 August 2026

моя красавица

custom 52648355077449550344

Signed tashia chan ´ω`

2 Aug 2026, 16:06 UTC93 views10 reactionsread 9 August 2026
Forwarded from @kawaiinunePhoto

#cos рт?

❤‍🔥5❤2custom 52807098528998557252💋1

Signed tashia chan ´ω`

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

31 Jul 2026, 17:41 UTCAnonymous Poll24 voters

Я очень сглупила, и забыла сделать опрос…Ну, сделаю сейчас

  1. Амэ-чан 😕42%
  2. Эна Шинономе🌟17%
  3. Мем Чо 😈33%
  4. Хёна🌟33%
  5. Гань Юй ✨42%
  6. Суа💜38%

The shares total 205%, 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.

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 15 most recent posts we hold, published 31 July 2026 to 8 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.

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 1 registered channel — 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.

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

“момока (няшева)” (@momokacos), 111 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/momokacos.

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.