Bot

Бот | Умскул

@maincourse_umschoolbot

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

13,514monthly users

-12,929 since we began measuring on 7 August 2026

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

Register entry

Telegram ID	6303148282
Type	Bot
Username	@maincourse_umschoolbot
First recorded	14 August 2026
Last confirmed live	27 August 2026
Measurements held	11
Confirmed unchanged	2 times, most recently 26 August 2026
On Telegram	t.me/maincourse_umschoolbot

Topic

Education — 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 73% 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

11 measurements spanning 18 days, net -12,929. 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 11,575–28,382 and does not start at zero.

Measurement log — every monthly users count we have recorded
Measured (UTC)	Monthly users	Change
25 Aug 2026, 14:44	13,514	-3,396
24 Aug 2026, 11:55	16,910	-1,500
22 Aug 2026, 17:55	18,410	-4,319
20 Aug 2026, 11:58	22,729	-2,823
18 Aug 2026, 13:05	25,552	-128
17 Aug 2026, 15:06	25,680	-271
14 Aug 2026, 20:44	25,951	no change
14 Aug 2026, 16:08	25,951	-261
12 Aug 2026, 07:03	26,212	-162
10 Aug 2026, 09:04	26,374	-69
7 Aug 2026, 21:57	26,443	first 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 42 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.

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.

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

“Бот | Умскул” (@maincourse_umschoolbot), 13,514 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/maincourse_umschoolbot.

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.