Telegram RegisterThe public register of Telegram
Telegram profile photo for Group Help

Bot

Group Help

@GHClone2Bot

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

348,659monthly users

-24,207 since we began measuring on 6 August 2026

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

Register entry

Telegram ID793977288
TypeBot
Username@GHClone2Bot
First recorded6 August 2026
Last confirmed live23 October 2026
Measurements held39
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/GHClone2Bot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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

348,659395,502372,080.56 August 2026 — 372,866 monthly users6 August 2026 — 372,866 monthly users7 August 2026 — 373,756 monthly users8 August 2026 — 374,624 monthly users11 August 2026 — 380,110 monthly users12 August 2026 — 369,994 monthly users13 August 2026 — 383,663 monthly users15 August 2026 — 386,029 monthly users16 August 2026 — 387,388 monthly users17 August 2026 — 379,968 monthly users18 August 2026 — 389,836 monthly users21 August 2026 — 381,130 monthly users22 August 2026 — 393,260 monthly users24 August 2026 — 392,661 monthly users25 August 2026 — 393,246 monthly users27 August 2026 — 395,044 monthly users29 August 2026 — 395,191 monthly users30 August 2026 — 395,502 monthly users31 August 2026 — 379,337 monthly users1 September 2026 — 388,464 monthly users3 September 2026 — 380,176 monthly users5 September 2026 — 375,348 monthly users8 September 2026 — 359,466 monthly users11 September 2026 — 358,877 monthly users13 September 2026 — 365,739 monthly users14 September 2026 — 374,577 monthly users16 September 2026 — 373,349 monthly users18 September 2026 — 371,944 monthly users25 September 2026 — 368,589 monthly users4 October 2026 — 376,294 monthly users8 October 2026 — 391,544 monthly users12 October 2026 — 393,510 monthly users14 October 2026 — 369,191 monthly users16 October 2026 — 368,721 monthly users17 October 2026 — 368,252 monthly users18 October 2026 — 366,723 monthly users21 October 2026 — 362,912 monthly users22 October 2026 — 357,306 monthly users23 October 2026 — 348,659 monthly users6 August 202623 October 2026
39 measurements spanning 78 days, net -24,207. 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 341,633–402,528 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 39
Measured (UTC)Monthly usersChange
23 Oct 2026, 13:35348,659-8,647
22 Oct 2026, 15:19357,306-5,606
21 Oct 2026, 06:11362,912-3,811
18 Oct 2026, 07:06366,723-1,529
17 Oct 2026, 05:30368,252-469
16 Oct 2026, 06:46368,721-470
14 Oct 2026, 11:46369,191-24,319
12 Oct 2026, 23:19393,510+1,966
8 Oct 2026, 13:57391,544+15,250
4 Oct 2026, 04:21376,294+7,705
25 Sept 2026, 11:01368,589-3,355
18 Sept 2026, 23:22371,944-1,405
16 Sept 2026, 12:20373,349-1,228
14 Sept 2026, 18:21374,577+8,838
13 Sept 2026, 08:00365,739+6,862
11 Sept 2026, 11:57358,877-589
8 Sept 2026, 16:19359,466-15,882
5 Sept 2026, 06:38375,348-4,828
3 Sept 2026, 11:57380,176-8,288
1 Sept 2026, 08:28388,464first 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 1 registered channel — 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.

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

“Group Help” (@GHClone2Bot), 348,659 monthly users as measured 23 October 2026. Telegram Register, tgregister.com/channel/GHClone2Bot.

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.