Telegram RegisterThe public register of Telegram
Telegram profile photo for EdСhess | Play Chess

Bot

EdСhess | Play Chess

@edchess

2 usernames

On this record: Topic · Growth · Engagement · Citations · Cite this entry

29,196monthly users

-18,402 since we began measuring on 6 August 2026

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

Register entry

Telegram ID6760906120
TypeBot
Usernames@edchess @edchess_bot
First recorded12 August 2026
Last confirmed live20 October 2026
Measurements held78
Confirmed unchanged1 time, most recently 20 October 2026
On Telegramt.me/edchess

Topic

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.

Growth

13,80847,59830,70329,1966 August 202620 October 2026
78 measurements spanning 75 days, net -18,402. 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,740–52,667 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 78
Measured (UTC)Monthly usersChange
20 Oct 2026, 06:0029,196no change
20 Oct 2026, 03:3929,196-867
19 Oct 2026, 06:0030,063no change
19 Oct 2026, 03:2130,063-1,077
17 Oct 2026, 06:4831,140no change
16 Oct 2026, 23:1731,140-255
16 Oct 2026, 05:5731,395no change
15 Oct 2026, 19:5631,395-604
15 Oct 2026, 06:0831,999no change
14 Oct 2026, 19:0831,999-1,000
14 Oct 2026, 01:3132,999no change
13 Oct 2026, 09:1832,999-859
11 Oct 2026, 10:5933,858-1,477
9 Oct 2026, 05:1935,335-445
7 Oct 2026, 03:0135,780+281
4 Oct 2026, 15:1535,499+528
2 Oct 2026, 04:5834,971+4,005
26 Sept 2026, 07:5830,966+7,089
19 Sept 2026, 08:4123,877+995
18 Sept 2026, 11:3722,882first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 21 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 20 October 2026 — this entry's latest reading, not the date you are reading this.

“EdСhess | Play Chess” (@edchess), 29,196 monthly users as measured 20 October 2026. Telegram Register, tgregister.com/channel/edchess.

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.