Channel
@skillchess
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
934subscribers
+24 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002082140696 |
|---|---|
| Type | Channel |
| Username | @skillchess |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/skillchess |
Gaming — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 06:19 | 934 | +6 |
| 9 Sept 2026, 18:37 | 928 | +11 |
| 31 Aug 2026, 02:24 | 917 | +5 |
| 24 Aug 2026, 22:53 | 912 | +5 |
| 17 Aug 2026, 11:27 | 907 | -3 |
| 10 Aug 2026, 23:18 | 910 | no change |
| 10 Aug 2026, 19:46 | 910 | first reading |
16 posts held, back to 27 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 16 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
33 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 22 | 66.7% | |
| 👏 | 5 | 15.2% | |
| 👍 | 3 | 9.09% | |
| 🔥 | 3 | 9.09% |
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 8 of the 16 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 33 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 27 July 2026 to 10 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.
Если после игры на Личессе вы всё ещё готовы смотреть на шахматную доску — мы знаем, куда идти. 😄♟️ Бар «Пешка» от RepChess — место, где даже коктейли остаются в шахматной теме: здесь можно заказать «Сицилианку» и другие дебютные напитки. 🍸 Бар находится в Москве, а от метро «Трубная» до него можно спокойно дойти даже без навигатора. Приходите отпраздновать победу 🏆, обсудить партии или просто вкусно «залить» пора…
🔥3
Video message, posted without a caption
❤6
Ответ к позиции : 1. Фg3 - ошибка, так как белые еще не закончили развитие 2. Черные спокойно могут сделать 0-0 и защитить пешку, продолжение атаки у белых нет, так как фигуры стоят на месте Вопрос : Как черным наказать белых ? Где атаковать ?
❤3
Бывает, смотришь на позицию и совершенно не понимаешь, какой ход сделать🧐. В такой ситуации не нужно гадать — достаточно пройти по простому алгоритму из 4️⃣ шагов! Рассказала про эти 4 шага в видео. Переходите смотреть👇 Ютуб https://youtu.be/x-bg9qayGaI Рутуб https://rutube.ru/video/a11518bd133c9799e9b0396b04fbc2b8/ Дзен https://dzen.ru/video/watch/6a721b8ca7fa8c037855beb0 ВК https://vkvideo.ru/video-211275905_4562…
1. Как вам ход Фg3 ? 2. Какой ход вы б ответили за черных на Фg3?
Здесь я белыми сыграла b7, далеко не лучший ход. Как бы вы сыграли белыми?
Здесь я играла черными, как бы вы сыграли?
В пятницу участвовала в нашем турнире по Итальянской партии (Марина). Предлагаю сегодня посмотреть пару позиций уже из моих партий. В этой я играла черными. Как думаете можно ли тут рубить Конь е5?
Ход белых, начать атаку на короля за Максима
👍2
Ход белых, продолжить атаку на короля, как Александр
Ход белых, попробуем найти как провел атаку здесь Дмитрий?
Video message, posted without a caption
❤3
Showing the 12 most recent of 16 posts we hold for @skillchess. 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.
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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Skill-chess.ru” (@skillchess), 934 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/skillchess.
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.