Telegram RegisterThe public register of Telegram

Channel

FC CREW MOSCOW

@crewmsk

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

103subscribers

+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-1002315882323
TypeChannel
Username@crewmsk
DescriptionАктуальные новости перспективного молодого клуба лиги AFL По поводу рекламы: t.me/alpachino83 Для коммерческих предложений: crewmoscowfc@gmail.com
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 live9 August 2026
Measurements held2
On Telegramt.me/crewmsk

Growth

1037 August 2026 — 103 subscribers9 August 2026 — 103 subscribers7 August 20269 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 102–104 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 09:46103no change
7 Aug 2026, 15:12103first reading

Engagement

20 posts held, back to 5 July 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 24 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
182
Videos
13
Links
23

Lifetime counters from Telegram’s own channel header, read 9 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.

Reaction mix

86 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 43.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3743.0%
2933.7%
😁910.5%
🤯44.65%
custom 532830866045405083133.49%
custom 540243523043277536333.49%
custom 535942028685477686111.16%

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

Measured over the 20 most recent posts we hold, published 5 July 2025 to 24 June 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
11
across the posts below
Posts paid on
5
of 20 we hold a reading for · 25%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @crewmsk. 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 20 most recent posts we hold for this entry, published 5 July 2025 to 24 June 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

10 Jun 2026, 14:38 UTC120 views1 reactions1 Starread 9 August 2026
Sticker

Sticker, posted without a caption

custom 53283086604540508311

4 Jun 2026, 12:37 UTC157 views1 reactions1 Starread 9 August 2026
Sticker

Sticker, posted without a caption

1

8 Apr 2026, 07:23 UTC224 views3 reactionsread 9 August 2026
Photo

😿 Очередной матч закончился очередным поражением. В этот раз мы продули 5:1. 🤨 Как говорил наш правый защитник на банке Джейсон Стетхем: «Летать авиакомпанией "Победа" — значит поражение». В отличие от самолетов Победы, наш самолет врезался в дерево неподалеку от Останкино, совершая полет в солнечную Италию на матч с Интером. Поэтому играть нам пришлось против Бедолаги. 🤣 Но вы все равно поддерживайте нас, например

🔥3

6 Apr 2026, 12:02 UTC149 views9 reactionsread 9 August 2026
Photo

😈 Мы проводим массовую чистку в канале 🤨 Мы забаним всех ботов в этом канале, чтобы поддерживалась дружелюбная атмосфера и соблюдались принципы открытой души по отношению к ближнему. 😈 Кто еще попадет под бан — люди, которые не поддерживают Crew Moscow. 😈 Чтобы подробнее изучить принципы, которых придерживается команда — обратите внимание на фотографию к посту. #aflrussia #CRmsk@crewmsk

😁5🔥4

5 Apr 2026, 13:48 UTC129 views2 reactionsread 9 August 2026
Photo

😀 Сегодня играем против «Bedolaga» во втором туре лиги AFL! 🔋 Приходите и поддерживайте нас на трансляции или вживую на поле в Останкино! #aflrussia #CRmsk@crewmsk

🔥2

1 Apr 2026, 09:58 UTC154 views4 reactionsread 9 August 2026
Photo

😣 Первый матч сезона закончился хуевым обидным поражением. 🎙 Началось все с того, что ковчег остановился на одной из гор Араратских. Аналогично ковчегу через тысячелетия черная Лада остановилась у поля в Измайлово. Оттуда вышел красавчик по имени Максимов. На этом моменте уже можно было не выходить на поле. 😄 Но мы вышли. Мы вышли и пинали мячик до конца. Пока силы нас не покинули, что произошло довольно скоро. ✅

😁4

29 Mar 2026, 07:03 UTC168 views3 reactionsread 9 August 2026
Photo

😈 Уже в сегодняшнем матче мы выйдем на поле против нашего первого соперника — «FC Chester». 💵 В 13:10 мы откроем сезон в новой лиге и снова будем стремиться к победе с ценным опытом побед и поражений, который мы получили в прошлом сезоне. 🤭 Следите за успехами вашей любимой команды через наши социальные сети и болейте за нас! #aflrussia #CRmsk@crewmsk

custom 540243523043277536321

29 Mar 2026, 04:01 UTC134 views4 reactionsread 9 August 2026
Photo

Crew Moscow входит в новый сезон AFL в дивизионе NorthEast 1 с сегодняшнего дня ✅ Приходите очно болеть за команду на стадион Zobnin Team (г. Москва, Измайловское шоссе, 73В, стр. 1) #aflrussia #CRmsk@crewmsk

🔥3custom 54024352304327753631

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

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“FC CREW MOSCOW” (@crewmsk), 103 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/crewmsk.

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.