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

Bot

Group Help

@grouphelp2bot

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

72,910monthly users

+8,699 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 ID233106564
TypeBot
Username@grouphelp2bot
First recorded11 August 2026
Last confirmed live9 October 2026
Measurements held21
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/grouphelp2bot

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 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 why it has no browse page of its own yet.

Growth

64,21180,21972,2156 August 2026 — 64,211 monthly users6 August 2026 — 67,435 monthly users10 August 2026 — 66,037 monthly users11 August 2026 — 66,037 monthly users14 August 2026 — 70,568 monthly users16 August 2026 — 70,083 monthly users19 August 2026 — 69,068 monthly users22 August 2026 — 68,854 monthly users24 August 2026 — 75,703 monthly users26 August 2026 — 77,480 monthly users29 August 2026 — 79,761 monthly users1 September 2026 — 80,219 monthly users5 September 2026 — 79,309 monthly users9 September 2026 — 77,621 monthly users11 September 2026 — 77,755 monthly users13 September 2026 — 78,011 monthly users17 September 2026 — 78,241 monthly users19 September 2026 — 78,713 monthly users26 September 2026 — 74,802 monthly users4 October 2026 — 71,205 monthly users9 October 2026 — 72,910 monthly users72,9106 August 20269 October 2026
21 measurements spanning 64 days, net +8,699. 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 61,810–82,620 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 21
Measured (UTC)Monthly usersChange
9 Oct 2026, 02:3872,910+1,705
4 Oct 2026, 14:5771,205-3,597
26 Sept 2026, 07:2174,802-3,911
19 Sept 2026, 11:1678,713+472
17 Sept 2026, 02:3778,241+230
13 Sept 2026, 17:5778,011+256
11 Sept 2026, 20:5877,755+134
9 Sept 2026, 09:2177,621-1,688
5 Sept 2026, 22:2079,309-910
1 Sept 2026, 14:2380,219+458
29 Aug 2026, 11:2779,761+2,281
26 Aug 2026, 17:4277,480+1,777
24 Aug 2026, 16:0275,703+6,849
22 Aug 2026, 23:1468,854-214
19 Aug 2026, 18:0569,068-1,015
16 Aug 2026, 07:1570,083-485
14 Aug 2026, 17:4870,568+4,531
11 Aug 2026, 16:4266,037no change
10 Aug 2026, 02:4166,037-1,398
6 Aug 2026, 20:4167,435first 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Group Help” (@grouphelp2bot), 72,910 monthly users as measured 9 October 2026. Telegram Register, tgregister.com/channel/grouphelp2bot.

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.