Telegram RegisterThe public register of Telegram

Channel

Mikkeller Cycling Club SPb | Перезагрузка

@mcc_spb

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

626subscribers

+4 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002930573249
TypeChannel
Username@mcc_spb
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/mcc_spb

Growth

6226266246 Aug 2026, 12:20 — 622 subscribers6 Aug 2026, 17:33 — 622 subscribers7 Aug 2026, 11:30 — 626 subscribers6 Aug 2026, 12:207 Aug 2026, 11:30
3 measurements taken within a single day, net +4. 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 621–627 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 11:30626+4
6 Aug 2026, 17:33622no change
6 Aug 2026, 12:20622first reading

Engagement

17 posts held, back to 26 July 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
87.1%
avg views ÷ 626 subscribers
Avg views / post
545
17 posts measured
Reaction rate
4.21%
reactions ÷ views · ER floor
Posts in window
17
of 17 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. It is computed over the 16 of 17 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held17 (26 July 20266 August 2026)
Views total9,268
Reactions total371
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 17:33 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.

Reaction mix

371 reactions across 16 posts, in 20 distinct kinds. The most used accounts for 32.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥12232.9%
6317.0%
custom 53280144895540023364512.1%
🎉369.70%
😁328.63%
👍195.12%
🤣164.31%
🥰92.43%
👏71.89%
🍓61.62%
🏆51.35%
🍌20.539%
🤝20.539%
custom 541817669788946675810.27%
10.27%
👀10.27%
😐10.27%
😢10.27%
🤔10.27%
🤩10.27%

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

Measured over the 17 most recent posts we hold, published 26 July 2026 to 6 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

6 Aug 2026, 13:33 UTC430 views12 reactionsread 6 August 2026
Photo

Завтра утром, 7 августа, СТАРТуем на коферайд от Газовой, 10 и финишируем там же! Сбор в 7:15, в 7:30 отправляемся на маршрут. Komoot: https://www.komoot.com/tour/2468162386 Дистанция: 20 км Темп: 25–27 км/ч Опрос и GPX в комментариях!

🔥10😢1custom 53280144895540023361

4 Aug 2026, 18:55 UTC326 views31 reactionsread 6 August 2026
Photo

📸 : 04 августа 2026. drink drank drunk встречают как родных! Всем спасибо за заезд!

🔥265

4 Aug 2026, 09:25 UTC361 views15 reactionsread 6 August 2026
Photo

Ребята, джерси приехали! (И даже с карманами.) Можно разбирать свои заказы!

8🔥5👏2

3 Aug 2026, 15:47 UTC378 views12 reactionsread 6 August 2026
Photo

По просьбам трудящихся обновили маршрут: см. GPX и по ссылке в анонсе!

😁12

3 Aug 2026, 08:09 UTC≈1,300 views15 reactionsread 6 August 2026
Photo

Всем городской заезд! Завтра, 4 августа, стартуем от нашей неповторимой базы — drink drank drunk. Сбор в 19:45, старт в 20:00. Маршрут (26 км): https://www.komoot.com/tour/3166296681 Темп 1: 27-32 км/ч Темп 2: 22-27 км/ч Ведущие: @maryoncycle & @avi4ulya_at_home На финише заветный изотоник и тёплый летний вечер! В комментариях к посту — GPX и опрос.

12🏆2🔥1

1 Aug 2026, 18:42 UTC436 views10 reactionsread 6 August 2026
Photo

Кто там думал насчёт завтрашнего лонграйда, отмечайтесь в опросе, надумали или нет. Всегда можно переголосовать. Утром может быть мокро, но по факту дальше должно распогодиться!

👏5custom 532801448955400233632

1 Aug 2026, 16:17 UTC425 views42 reactionsread 6 August 2026
Photo

📸 : 01 августа 2026. Залетели в Москву!

🎉32🍓6🔥4

31 Jul 2026, 10:25 UTC798 views13 reactionsread 6 August 2026
Photo

Всем привет! В это воскресенье, 2 августа, @triplemel приглашает всех разделить с ним интересный лонграйд в Васкелово. Сбор в 10:00 у кафе Старт (Газовая ул., 10), старт в 10:30. Маршрут 81 км: https://mapmagic.app/map?routes=0w8Ddp6 Темп: 25–30 км/ч Планируется остановка на пляже около Медного озера (50 км маршрута), перед этим заедем в Пятёрочку пополнить запасы ништяков на перекус. Домой возвращаемся на электричк

🔥7👍41🤩1

31 Jul 2026, 07:52 UTC488 views21 reactionsread 6 August 2026

Ванечка видосик записал на память: https://youtu.be/b_gGadVh0Ro?si=A4E4Xs3rzs_aF2y6

🔥12custom 53280144895540023367🍌2

31 Jul 2026, 06:55 UTC461 viewsread 6 August 2026

Кто вчера на заезде фонарь Rockbros потерял?

30 Jul 2026, 20:26 UTC494 views42 reactionsread 6 August 2026
Photo

📸 : 30 июля 2026. Купчино здесь!

24🔥14🏆31

30 Jul 2026, 09:28 UTC477 views23 reactionsread 6 August 2026
Photo

Сегодня едем! 🙂 На финише вас, помимо изотоника, будут ждать РОЗЫГРЫШ лотов с соревнований от Маши и Кирилла, а если ещё кто хотел клубных СТИКЕРОВ взять — они тоже будут. До встречи!

🔥12🥰6👍31🤔1

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

Citation-graph rank

Citation-graph rank — 387,974 of 1,169,250entries 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

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

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

“Mikkeller Cycling Club SPb | Перезагрузка” (@mcc_spb), 626 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/mcc_spb.

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.