Telegram RegisterThe public register of Telegram
Telegram profile photo for Moss // Михаил Моссаковский

Channel

Moss // Михаил Моссаковский

@mossakovskiy

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

8,508subscribers

+170 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001303032981
TypeChannel
Username@mossakovskiy
DescriptionБлог Михаила Моссаковского ⚽️ № 5055247262 По вопросам сотрудничества и предложениям: [email protected]
Created12 October 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live5 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/mossakovskiy

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 52% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

8,2938,5088,400.56 August 2026 — 8,338 subscribers6 August 2026 — 8,338 subscribers6 August 2026 — 8,342 subscribers10 August 2026 — 8,328 subscribers12 August 2026 — 8,320 subscribers16 August 2026 — 8,314 subscribers19 August 2026 — 8,325 subscribers22 August 2026 — 8,342 subscribers25 August 2026 — 8,331 subscribers28 August 2026 — 8,322 subscribers31 August 2026 — 8,326 subscribers3 September 2026 — 8,321 subscribers9 September 2026 — 8,307 subscribers13 September 2026 — 8,293 subscribers17 September 2026 — 8,317 subscribers27 September 2026 — 8,294 subscribers5 October 2026 — 8,352 subscribers11 October 2026 — 8,333 subscribers14 October 2026 — 8,361 subscribers18 October 2026 — 8,372 subscribers21 October 2026 — 8,402 subscribers24 October 2026 — 8,396 subscribers27 October 2026 — 8,464 subscribers30 October 2026 — 8,488 subscribers2 November 2026 — 8,506 subscribers5 November 2026 — 8,508 subscribers6 August 20265 November 2026
26 measurements spanning 91 days, net +170. 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 8,261–8,540 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
5 Nov 2026, 02:508,508+2
2 Nov 2026, 08:468,506+18
30 Oct 2026, 17:148,488+24
27 Oct 2026, 14:558,464+68
24 Oct 2026, 07:278,396-6
21 Oct 2026, 01:398,402+30
18 Oct 2026, 04:078,372+11
14 Oct 2026, 23:458,361+28
11 Oct 2026, 14:168,333-19
5 Oct 2026, 13:208,352+58
27 Sept 2026, 08:598,294-23
17 Sept 2026, 17:368,317+24
13 Sept 2026, 05:568,293-14
9 Sept 2026, 06:158,307-14
3 Sept 2026, 20:398,321-5
31 Aug 2026, 07:078,326+4
28 Aug 2026, 16:248,322-9
25 Aug 2026, 07:528,331-11
22 Aug 2026, 03:378,342+17
19 Aug 2026, 07:058,325first reading

Engagement

92 posts held, back to 1 August 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 27 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
29.2%
avg views ÷ 8,508 subscribers
Avg views / post
2,480
23 posts measured
Reaction rate
2.55%
reactions ÷ views · ER floor
Posts in window
23
of 92 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 November 2026
Posts held92 (1 August 2026 – 5 November 2026)
Views total57,093
Reactions total1,454
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 10:24 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.

What this channel posts

Photos
≈1,510
Videos
≈705
Links
≈1,700

Lifetime counters from Telegram’s own channel header, read 5 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
9m 38s
Average length
34s

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

4,470 reactions across 88 posts, in 34 distinct kinds. The most used accounts for 30.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,37130.7%
👍79517.8%
🔥67815.2%
😁54712.2%
💯1733.87%
🤣1593.56%
👎942.10%
🤡801.79%
💩761.70%
👏561.25%
😱561.25%
🤯481.07%
😢461.03%
❤‍🔥390.872%
🎉360.805%
👀270.604%
🕊260.582%
🤔240.537%
💔220.492%
🙏220.492%
14 further kinds952.13%

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 90 of the 92 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 4,603 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 92 most recent posts we hold, published 1 August 2026 to 5 November 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

Telegram’s own ‘edited’ marker: 6 of 23 posts held from the last 30 days (26.1%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

5 Nov 2026, 07:57 UTC203 views7 reactionsread 5 November 2026
Forwarded from @QryaProDucktionPhoto

Аукцион в поддержку нашего маленького друга Влада! Мы уже рассказывали вам про его тяжелую болезнь и вместе не раз помогали Владу. «Футбольный клуб» Василия Уткина» совместно с ЦСКА предлагает вам снова помочь мальчику. Мы выставляем на аукцион футболку с автографами всей команды армейцев: от молодого таланта Матвея Кисляка до капитана Игоря Акинфеева. Аукцион пройдет в комментариях под этим постом. А все вырученн…

🙏6❤1

4 Nov 2026, 21:06 UTC≈1,360 views27 reactionsread 5 November 2026
Photo

Ну нет, Нико Пас здесь больше похож на уменьшенную копию Николая Валуева. А двойник - Эстебана Камбьяссо - это Евгений Болотов из Оренбурга. И внешне, и даже по позиции. https://t.me/Chepa98/4243

❤18🤣9

4 Nov 2026, 10:31 UTC≈1,750 views90 reactionsread 5 November 2026
Photo

Лучший вариант, чтобы загадать желание. Два Александра. Два Викторовича. Две легенды. Жгучий лайк обоим 🔥🔥👍👍

🔥63❤10👍10🤡3😁3❤‍🔥1

3 Nov 2026, 19:32 UTC≈2,110 views114 reactionsread 5 November 2026

4 гола в 4 матчах ЛЧ. Ни один российский игрок еще не стартовал в Лиге Чемпионов с такой результативностью. Алексей Батраков рубит окно в Европу. Прикройте глаза, а то щепки летят.

❤91👍13🥰5🔥3🤡2

2 Nov 2026, 10:23 UTC≈2,370 views23 reactionsread 5 November 2026
Photo

Реплика по 13 туру готова! Сеча в Оренбурге. Краснодар без амбиций. Спартак на ходу. Худшая неделя Локо при Галактионове. Прагматичное Динамо. Круговорот тренеров. И немного про открытость арбитров. 📺 Видео на Ютуб 🔹 Видео в ВК

❤23

1 Nov 2026, 19:01 UTC≈3,000 views117 reactionsread 5 November 2026

Крушение Локо. И проще всего сделать в нем крайним тренера команды. Но не вина Галактионова в том, что один за другим были распроданы лидеры команды прошлого сезона. И когда команду, вошедшую в прошлом году в медали, буквально разобрали по кирпичу, удержать ментальность раздевалки мог бы только самый топовый коуч. Можно ли упрекать Галактионова в том, что он не удержал команду от пике? На мой взгляд, тренер не засл…

👍85🤡15❤10👎7

1 Nov 2026, 17:24 UTC≈4,460 views62 reactionsread 5 November 2026
Photo

Реакция Максименко на гол Парады бесценна. Не ждали (с)

😁40❤17🔥4🤮1

1 Nov 2026, 16:26 UTC≈2,190 views55 reactionsread 5 November 2026
Forwarded from @rustime_96Video

САМ ПСИХАНУЛ. САМ ПОРАДОВАЛСЯ.

😁52❤3

1 Nov 2026, 16:02 UTC≈2,840 views37 reactionsread 5 November 2026
Video

Это точно не фол? Общепризнанных компетенций ноль, не спорю. Но все же… Почему это не пенальти? Объясните, товарищи эксперты.

😁24🤷‍♀6❤3🖕3🤷‍♂1

1 Nov 2026, 15:05 UTC≈2,740 views42 reactionsread 5 November 2026
Video

Кажется, пока это сейв ноября. Латышонок 🔝

👎20❤16👍6

1 Nov 2026, 13:46 UTC≈2,680 views59 reactionsread 5 November 2026
Video

Пока самое яркое игровое действие дня. Гол Кости Кучаева в стиле Зидана. Высший пилотаж.

👍41👏10❤8

1 Nov 2026, 09:03 UTC≈2,020 views21 reactionsread 5 November 2026
Forwarded from @matchpremierPhoto

Отметим праздничный день с любимой лигой и дерби.

❤15👍6

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

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 32 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Здесь был Тимур | Тимур Журавель
@timzhur · 26,459
Telegram ranks this channel #22 of 100 here — alongside 99 others — read 12 September 2026
Nobel
@nobel_arustamyan · 39,139
Telegram ranks this channel #48 of 100 here — alongside 99 others — read 30 August 2026
Сплошняк | Дмитрий Шнякин
@shhhnyakin · 38,840
Telegram ranks this channel #52 of 99 here — alongside 98 others — read 31 August 2026
Брейдо / И после
@BreydoChannel · 21,398
Telegram ranks this channel #57 of 98 here — alongside 97 others — read 24 September 2026
Будни Бобана
@BudniBobana · 23,852
Telegram ranks this channel #61 of 95 here — alongside 94 others — read 17 September 2026
Коммент.Генич
@kgenich · 52,419
Telegram ranks this channel #67 of 100 here — alongside 99 others — read 24 August 2026
ЭкСпорт Клипина
@xsport24 · 37,699
Telegram ranks this channel #68 of 99 here — alongside 98 others — read 1 September 2026
Казанский Код
@deniskazansky · 24,332
Telegram ranks this channel #72 of 100 here — alongside 99 others — read 17 September 2026

This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Moss // Михаил Моссаковский” (@mossakovskiy), 8,508 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/mossakovskiy.

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.