Telegram RegisterThe public register of Telegram
Telegram profile photo for Сделать кружок из видео, кружки ТГ 📺

Bot

Сделать кружок из видео, кружки ТГ 📺

@tgcRobot

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

38,760monthly users

-746 since we began measuring on 6 August 2026

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

Register entry

Telegram ID7603376279
TypeBot
Username@tgcRobot
First recorded12 August 2026
Last confirmed live6 November 2026
Measurements held40
Confirmed unchanged2 times, most recently 6 November 2026
On Telegramt.me/tgcRobot

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

37,89145,64241,766.56 August 2026 — 39,506 monthly users7 August 2026 — 39,845 monthly users9 August 2026 — 39,846 monthly users12 August 2026 — 39,846 monthly users12 August 2026 — 40,003 monthly users15 August 2026 — 40,648 monthly users18 August 2026 — 40,971 monthly users20 August 2026 — 41,008 monthly users22 August 2026 — 40,992 monthly users25 August 2026 — 40,865 monthly users26 August 2026 — 41,939 monthly users28 August 2026 — 42,468 monthly users29 August 2026 — 42,609 monthly users31 August 2026 — 42,959 monthly users31 August 2026 — 43,100 monthly users3 September 2026 — 43,511 monthly users4 September 2026 — 43,435 monthly users6 September 2026 — 43,644 monthly users10 September 2026 — 42,630 monthly users12 September 2026 — 43,170 monthly users13 September 2026 — 44,032 monthly users17 September 2026 — 44,376 monthly users25 September 2026 — 45,642 monthly users4 October 2026 — 42,713 monthly users8 October 2026 — 42,500 monthly users12 October 2026 — 42,167 monthly users14 October 2026 — 41,153 monthly users16 October 2026 — 39,200 monthly users17 October 2026 — 39,836 monthly users19 October 2026 — 39,675 monthly users20 October 2026 — 39,072 monthly users21 October 2026 — 38,626 monthly users23 October 2026 — 37,957 monthly users25 October 2026 — 37,891 monthly users27 October 2026 — 37,904 monthly users29 October 2026 — 38,081 monthly users30 October 2026 — 38,161 monthly users1 November 2026 — 38,335 monthly users3 November 2026 — 38,846 monthly users5 November 2026 — 38,760 monthly users38,7606 August 20265 November 2026
40 measurements spanning 91 days, net -746. 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 36,728–46,805 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 40
Measured (UTC)Monthly usersChange
5 Nov 2026, 02:4938,760-86
3 Nov 2026, 04:5138,846+511
1 Nov 2026, 04:2938,335+174
30 Oct 2026, 05:0038,161+80
29 Oct 2026, 08:2838,081+177
27 Oct 2026, 00:3437,904+13
25 Oct 2026, 21:4537,891-66
23 Oct 2026, 20:2937,957-669
21 Oct 2026, 16:3638,626-446
20 Oct 2026, 13:4739,072-603
19 Oct 2026, 13:5139,675-161
17 Oct 2026, 16:2039,836+636
16 Oct 2026, 14:5539,200-1,953
14 Oct 2026, 14:0441,153-1,014
12 Oct 2026, 23:4942,167-333
8 Oct 2026, 16:4042,500-213
4 Oct 2026, 06:4242,713-2,929
25 Sept 2026, 17:4045,642+1,266
17 Sept 2026, 12:1644,376+344
13 Sept 2026, 22:3744,032first 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.

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

“Сделать кружок из видео, кружки ТГ 📺” (@tgcRobot), 38,760 monthly users as measured 5 November 2026. Telegram Register, tgregister.com/channel/tgcRobot.

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.