Telegram RegisterThe public register of Telegram

Channel

Играем в Го

@weplaygo

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

1,204subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001748996321
TypeChannel
Username@weplaygo
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/weplaygo

Growth

1,2021,2051,203.56 August 2026 — 1,202 subscribers7 August 2026 — 1,202 subscribers10 August 2026 — 1,205 subscribers13 August 2026 — 1,204 subscribers1,2046 August 202613 August 2026
4 measurements spanning 6 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 1,202–1,205 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 06:331,204-1
10 Aug 2026, 06:401,205+3
7 Aug 2026, 03:351,202no change
6 Aug 2026, 23:171,202first reading

Engagement

20 posts held, back to 13 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
39.5%
avg views ÷ 1,204 subscribers
Avg views / post
476
17 posts measured
Reaction rate
2.71%
reactions ÷ views · ER floor
Posts in window
17
of 20 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 5 August 2026
Posts held20 (13 July 20265 August 2026)
Views total8,090
Reactions total206
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 23:17 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

242 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 33.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥8233.9%
👍6727.7%
6426.4%
👌104.13%
🎉93.72%
custom 539082060807223255452.07%
🤔52.07%

Custom emoji. One row above is a 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 count beside it isTelegram’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 19 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 242reactions 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 13 July 2026 to 5 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

5 Aug 2026, 21:26 UTC221 views10 reactionsread 6 August 2026
Video

🔥 Выпущенный Го-клубом «Играем в Го» набор карточек с формами и ходами можно использовать как универсальный инструмент для любителей Го. Он подходит и для первого знакомства малышей с доской и камнями, и для обучения использованию форм, а между партиями для увлекательных настольных игр. Набор делает ярким каждое занятие с детьми и подростками! На сайте книги в разделе полезных файлов опубликованы материалы, открытые

👍3🔥32custom 53908206080722325542

4 Aug 2026, 22:48 UTC285 views12 reactionsread 6 August 2026

В битве топ-16 уже состоялись 4 партии из 8, хотя прошло всего 2 дня четвертого тура. Мы обновили страницу верхней группы, и теперь сразу после партии игроки из нее автоматически показываются в таблице следующего тура. UPD: При наведении на игрока в одной из партий в этой таблице он подсвечивается во всех остальных партиях, что уже сыграл или должен сыграть. Так лучше удобнее видеть путь игрока через туры. #играемг

5👍4🔥3

3 Aug 2026, 12:13 UTC309 views10 reactionsread 6 August 2026
Photo

🏆 В рамках «Летнего кубка» набирает обороты клубный зачет. Клубы уже получили первые очки за выход своих представителей в топ-16, ведь эти игроки гарантированно займут места не ниже шестнадцатого и принесут своим командам минимум один бал. Давайте посмотрим, какие клубы вышли вперед по числу участников в верхней сетке: - Sente (Москва) – 3 игрока - Никонико (Николаевск-на-Амуре) – 2 игрока - МГУ (Москва) – 1 игрок -

🔥5👍32

3 Aug 2026, 10:23 UTC292 views15 reactionsread 6 August 2026
Photo

Летний кубок «Играем в Го» переходит на новый уровень! Начинаются сражения в группе топ-16, где закрепились сильнейшие участники. Следить за ходом битвы можно на специальной странице. Все самое интересное только начинается. ⚔️ В текущем туре схема турнира сводит игроков со сдвигом на восемь позиций: первый номер играет с девятым, второй – с десятым и далее по списку. Участникам из верхней восьмерки предстоит доказат

6🔥5👍4

3 Aug 2026, 04:02 UTC311 views10 reactionsread 6 August 2026
Photo

Проведена жеребьевка 4 тура Летнего кубка «Играем в Го». Чтобы быстро узнать контакты своего соперника, запустите нашего клубного бота @weplaygobot и отправьте ему команду /tour Используйте контакты для согласования дня и времени партии. Напишите в Telegram или отправьте сообщение через бота. Не получили ответ в течение нескольких часов днем? Тогда напомните о себе еще раз, а если и это не поможет, то пишите СМС или

👍5🔥32

27 Jul 2026, 14:08 UTC≈1,010 views17 reactionsread 6 August 2026
Photo

Знаете ли вы, что закладывать основы сильного мышления и эмоционального интеллекта можно с самого раннего детства? Игра Го – это не просто древняя стратегия, а мощный тренажер для ума. И незаменимым помощником на этом пути станет книга «Играем в Го с малышами» Даниила Кальченко, выпущенная клубом «Играем в Го». 🧠 Интеллектуальный потенциал ребенка активно формируется именно в первые годы жизни. Кажется, что Го – это

8🔥6custom 53908206080722325543

27 Jul 2026, 10:46 UTC476 views13 reactionsread 6 August 2026
Photo

Командный зачет Летнего кубка «Играем в Го» набирает обороты! Мы запустили специальную страницу, где будет обновляться таблица с клубами. Совсем скоро, сразу после 3-го тура, там появятся первые результаты. Сохраняйте ссылку и следите за гонкой! ✨ 6 клубов сформировали команды и активно борются за лидерство в Летнем кубке. География участников действительно впечатляет: - Никонико (Николаевск-на-Амуре) – 10 игроков -

👍73🔥3

27 Jul 2026, 04:04 UTC486 views13 reactionsread 6 August 2026
Photo

Проведена жеребьевка 3 тура Летнего кубка «Играем в Го». Чтобы быстро узнать контакты своего соперника, запустите нашего клубного бота @weplaygobot и отправьте ему команду /tour Используйте контакты для согласования дня и времени партии. Напишите в Telegram или отправьте сообщение через бота. Не получили ответ в течение нескольких часов днем? Тогда напомните о себе еще раз, а если и это не поможет, то пишите СМС или

🔥64👍3

21 Jul 2026, 22:21 UTC619 views7 reactionsread 6 August 2026
Poll

На каких электронных устройствах вы играете партии Летнего кубка?

  1. Десктоп20%
  2. Ноутбук42%
  3. Планшет8%
  4. Смартфон14%
  5. Посмотреть31%

The shares total 115%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

👌3👍2🔥2

21 Jul 2026, 10:47 UTC592 views14 reactionsread 6 August 2026
Photo

Пришло время раскрыть схему проведения партий в верхней группе среди топ-16 игроков Летнего кубка «Играем в Го». На сайте турнира уже появилась новая страница, посвященная этому этапу. Предлагаем вам изучить сетку и оценить масштаб предстоящих сражений. 📈 Все начнется с тура, где игроки встретятся со сдвигом на 8 позиций: 1-й сыграет с 9-м, 2-й с 10-м и так далее. Этот шаг позволит подтвердить статус сильнейших. По

🔥63🤔3🎉2

21 Jul 2026, 08:57 UTC460 views23 reactionsread 6 August 2026

Син Чинсо победил KataGo в третьей партии турнира! Подробности в комментариях в цитируемом посту! 🎉

🔥12🎉72👍2

20 Jul 2026, 23:35 UTC500 viewsread 6 August 2026
Poll

Кто победит в третьей партии матча между KataGo и Син Чинсо?

  1. KataGo30%
  2. Син Чинсо55%
  3. Посмотреть16%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

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

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

21 Jul 2026, 22:21 UTCAnonymous Poll86 voters

На каких электронных устройствах вы играете партии Летнего кубка?

  1. Десктоп20%
  2. Ноутбук42%
  3. Планшет8%
  4. Смартфон14%
  5. Посмотреть31%

The shares total 115%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

20 Jul 2026, 23:35 UTCFinal Results64 voters

Кто победит в третьей партии матча между KataGo и Син Чинсо?

  1. KataGo30%
  2. Син Чинсо55%
  3. Посмотреть16%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 13 July 2026 to 5 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 64,950 of 1,336,469entries 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

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 5 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.

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

“Играем в Го” (@weplaygo), 1,204 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/weplaygo.

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.