Telegram RegisterThe public register of Telegram
Telegram profile photo for C‌O‌L‌O‌R‌S‌U‌B𓂃

Bot

C‌O‌L‌O‌R‌S‌U‌B𓂃

@ColorSub_bot

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

30,346monthly users

-658 since we began measuring on 8 August 2026

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

Register entry

Telegram ID8370786708
TypeBot
Username@ColorSub_bot
First recorded14 August 2026
Last confirmed live8 November 2026
Measurements held50
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/ColorSub_bot

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

29,24731,43230,339.58 August 2026 — 31,004 monthly users9 August 2026 — 30,957 monthly users11 August 2026 — 30,909 monthly users12 August 2026 — 30,876 monthly users14 August 2026 — 30,497 monthly users14 August 2026 — 30,497 monthly users15 August 2026 — 30,509 monthly users16 August 2026 — 30,643 monthly users17 August 2026 — 30,425 monthly users18 August 2026 — 30,660 monthly users19 August 2026 — 30,709 monthly users20 August 2026 — 30,335 monthly users23 August 2026 — 29,954 monthly users24 August 2026 — 30,274 monthly users27 August 2026 — 29,894 monthly users28 August 2026 — 29,509 monthly users29 August 2026 — 29,405 monthly users30 August 2026 — 29,451 monthly users31 August 2026 — 30,013 monthly users1 September 2026 — 30,171 monthly users3 September 2026 — 30,141 monthly users4 September 2026 — 29,247 monthly users7 September 2026 — 29,656 monthly users10 September 2026 — 29,808 monthly users12 September 2026 — 30,236 monthly users14 September 2026 — 30,879 monthly users16 September 2026 — 30,980 monthly users18 September 2026 — 30,845 monthly users2 October 2026 — 31,339 monthly users7 October 2026 — 31,432 monthly users11 October 2026 — 31,126 monthly users15 October 2026 — 30,779 monthly users16 October 2026 — 30,295 monthly users17 October 2026 — 30,145 monthly users18 October 2026 — 30,218 monthly users20 October 2026 — 30,480 monthly users22 October 2026 — 30,214 monthly users24 October 2026 — 29,824 monthly users25 October 2026 — 29,863 monthly users26 October 2026 — 30,131 monthly users28 October 2026 — 30,168 monthly users30 October 2026 — 29,716 monthly users31 October 2026 — 29,799 monthly users1 November 2026 — 29,855 monthly users2 November 2026 — 30,147 monthly users3 November 2026 — 30,218 monthly users5 November 2026 — 30,116 monthly users6 November 2026 — 29,916 monthly users7 November 2026 — 29,820 monthly users8 November 2026 — 30,346 monthly users30,3468 August 20268 November 2026
50 measurements spanning 92 days, net -658. 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 28,919–31,760 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 50
Measured (UTC)Monthly usersChange
8 Nov 2026, 16:0630,346+526
7 Nov 2026, 08:4929,820-96
6 Nov 2026, 07:4629,916-200
5 Nov 2026, 08:2730,116-102
3 Nov 2026, 07:0830,218+71
2 Nov 2026, 06:2630,147+292
1 Nov 2026, 04:5929,855+56
31 Oct 2026, 07:0529,799+83
30 Oct 2026, 09:0829,716-452
28 Oct 2026, 05:5030,168+37
26 Oct 2026, 04:0630,131+268
25 Oct 2026, 04:2029,863+39
24 Oct 2026, 04:5629,824-390
22 Oct 2026, 07:1630,214-266
20 Oct 2026, 00:0530,480+262
18 Oct 2026, 04:5030,218+73
17 Oct 2026, 06:2630,145-150
16 Oct 2026, 09:2830,295-484
15 Oct 2026, 07:5730,779-347
11 Oct 2026, 22:5531,126first 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 3 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 8 November 2026 — this entry's latest reading, not the date you are reading this.

“C‌O‌L‌O‌R‌S‌U‌B𓂃” (@ColorSub_bot), 30,346 monthly users as measured 8 November 2026. Telegram Register, tgregister.com/channel/ColorSub_bot.

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.