Telegram RegisterThe public register of Telegram
Telegram profile photo for ФК Мишель и К

Channel

ФК Мишель и К

@mishelandk

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

493subscribers

+2 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-1002670289294
TypeChannel
Username@mishelandk
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/mishelandk

Growth

4914934927 August 2026 — 491 subscribers8 August 2026 — 491 subscribers15 August 2026 — 493 subscribers22 August 2026 — 491 subscribers28 August 2026 — 492 subscribers7 September 2026 — 493 subscribers7 August 20267 September 2026
6 measurements spanning 31 days, net +2. 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 491–493 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 09:40493+1
28 Aug 2026, 18:58492+1
22 Aug 2026, 05:56491-2
15 Aug 2026, 20:25493+2
8 Aug 2026, 04:20491no change
7 Aug 2026, 08:48491first reading

Engagement

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

What this channel posts

Video runtime
4m 34s
Average length
55s

Measured directly from 5 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

161 reactions across 15 posts, in 13 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6238.5%
🔥3119.3%
👍2314.3%
🏆169.94%
👏95.59%
🙏53.11%
🥰42.48%
31.86%
😍31.86%
🤣21.24%
🌭10.621%
🙉10.621%
🤝10.621%

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 15 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 161 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 10 May 2026 to 31 May 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

31 May 2026, 13:40 UTC566 views17 reactionsread 8 August 2026
Forwarded from @sffsiberiaPhoto

Первые три очка для команды «Мишель и К» в этом сезоне ⚡️ 💜 — ⚽️ | «Мишель и К» г. Томск — «ШахтоСтрой» г. Абаза — 3:0 (1:0) Голы: Науменко 25', 61', Салахутдинов 65'. 📺 Записи матчей ⚽️⚽️⚽️⚽️ @sffsiberia ⚽️ | «Сибирь» в MAX

🏆9🥰4🙏21😍1

30 May 2026, 04:22 UTC679 views15 reactionsread 8 August 2026
Photo

Уже завтра стартуем в Третьей Лиге Сибирь «Серебро» ⚡️ В первом матче сезона сыграем с новичком лиги из Абазы ⚽ Стадион «Темп» 31 мая 15:00 | «Мишель и К» г. Томск — «ШахтоСтрой» г. Абаза

🔥10🙏311

27 May 2026, 06:23 UTC641 views1 reactionsread 8 August 2026
Forwarded from @sffsiberiaPhoto

⚡ Официальное заявление Союза федераций футбола «Сибирь» Команда «КДВ-М» (Томск) официально снимается с розыгрыша Третьей Лиги Сибирь «Серебро». Данное решение принято руководством футбольного клуба «КДВ-М». По заявлению клуба – «КДВ-2» продолжает выступление в Третьей лиге Сибирь «Золото». Изменения в календаре матчей Третьей Лиги Сибирь «Серебро» на май: 29 мая – «Ермак» г. Томск – «ШахтоСтрой» г. Абаза Матч,

1

23 May 2026, 10:35 UTC630 views24 reactionsread 8 August 2026
Video

Пооообееееедааа 2:1 😍

20😍21🏆1

23 May 2026, 06:44 UTC581 views3 reactionsread 8 August 2026

Ссылка на сегодняшний матч 1/8 Кубка Сибири

🔥21

23 May 2026, 03:52 UTC568 views5 reactionsread 8 August 2026

Флеш-интервью со вчерашней предыгровой тренировки в Барнауле 🏆 Ссылка на видео

👍2🔥21

22 May 2026, 12:43 UTC501 views1 reactionsread 8 August 2026
Forwarded from @sffsiberiaPhoto

1/8 финала Кубка Сибири 2026 уже завтра! 🏆 23 мая команды проведут свои первые матчи в серии: 13:00 | 🤍 — 💚 | «Динамо-Барнаул-2» г. Барнаул — «СШ-Гудаута» г. Бердск 13:00 | 💧 — ⚽️ | «Байкал» г. Иркутск — «БРАТСКШИНА» г. Братск 15:00 | ⚽️ — ❄️ | «КДВ-2» г. Томск — «Сибирь-М» г. Новосибирск 15:00 | ❣️ — 💜 | «Полимер» г. Барнаул — «Мишель и К» г. Томск 17:00 | 🦁 — 🦁 | «Енисей-М» г. Красноярск — «Рассвет» г. Красно

1

22 May 2026, 07:04 UTC419 views6 reactionsread 8 August 2026
Forwarded from @sffsiberiaVideo

Сибирь живёт! 🎶 Уже завтра стартует 1/8 финала Кубка Сибири 2026 🏆 @sffsiberia ⚽️ | «Сибирь» в MAX

3👍1🔥1🤣1

21 May 2026, 15:53 UTC459 views8 reactionsread 8 August 2026

Уже завтра утром выдвигаемся в сторону Барнаула, где в субботу нас ждёт кубковый матч против местного «Полимера»🤘💚🏆 Давайте послушаем наших ребят, что они думают по поводу прошедшего матча с «Ермаком» и предстоящего матча 1/8 Кубка Сибири 💯 Ссылка на интервью

5👍2🔥1

14 May 2026, 15:09 UTC651 views5 reactionsread 8 August 2026

Видеообзор матча предварительного этапа Кубка Сибири с Ермаком 🫨

👍2🔥21

12 May 2026, 08:08 UTC630 views11 reactionsread 8 August 2026
Forwarded from @sffsiberiaPhoto

А что, если попросить нейросеть нарисовать прошедшие матчи предварительных этапов Кубка Сибири — 2026? 📸 @sffsiberia ⚽️ | «Сибирь» в MAX

6👍3🔥2

10 May 2026, 13:19 UTC598 views11 reactionsread 8 August 2026
Forwarded from @sffsiberiaPhoto

Предварительные этапы Кубка Сибири 2026 года завершились матчами в Томске и Братске 🏆 «БРАТСКШИНА» в 1/8 финала сыграет с «Байкалом», «Ермак» с «Темпом», а «Мишель и К» с «Полимером». 💜 — 🕶 | «Мишель и К» г. Томск — «Ермак» г. Томск — 4:0 (2:0) Голы: Козлов 35', 39', Науменко 56', Роговцев 65'. ⚽️ — 🎩 | «БРАТСКШИНА» г. Братск — «Шахтёр» г. Черемхово — 1:1 (0:1) Голы: Ломов 90' — Евдокимов 5'. 📺 Записи матчей @sf

8🏆2🔥1

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

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.

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

“ФК Мишель и К” (@mishelandk), 493 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/mishelandk.

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.