Telegram RegisterThe public register of Telegram
Telegram profile photo for X_GSM_TEAM_Chat

Supergroup

X_GSM_TEAM_Chat

@X_GSM_TEAM_CHAT

Has discussion group

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

1,954members

+59 since we began measuring on 7 August 2026

182 online right now

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

Register entry

Telegram ID-1001164172531
TypeSupergroup
Username@X_GSM_TEAM_CHAT
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded22 September 2026
Last confirmed live31 October 2026
Measurements held24
Confirmed unchanged1 time, most recently 31 October 2026
On Telegramt.me/X_GSM_TEAM_CHAT

Topic

Software piracy — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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

1,8781,9541,9167 August 2026 — 1,895 members8 August 2026 — 1,892 members11 August 2026 — 1,897 members15 August 2026 — 1,893 members18 August 2026 — 1,894 members21 August 2026 — 1,887 members24 August 2026 — 1,886 members27 August 2026 — 1,887 members30 August 2026 — 1,886 members2 September 2026 — 1,884 members7 September 2026 — 1,892 members11 September 2026 — 1,887 members15 September 2026 — 1,880 members19 September 2026 — 1,878 members22 September 2026 — 1,878 members29 September 2026 — 1,892 members6 October 2026 — 1,904 members12 October 2026 — 1,918 members16 October 2026 — 1,921 members19 October 2026 — 1,922 members22 October 2026 — 1,926 members25 October 2026 — 1,949 members28 October 2026 — 1,952 members31 October 2026 — 1,954 members7 August 202631 October 2026
24 measurements spanning 85 days, net +59. 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 1,867–1,965 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 24
Measured (UTC)MembersChange
31 Oct 2026, 08:541,954+2
28 Oct 2026, 01:301,952+3
25 Oct 2026, 11:301,949+23
22 Oct 2026, 06:461,926+4
19 Oct 2026, 06:091,922+1
16 Oct 2026, 04:371,921+3
12 Oct 2026, 22:571,918+14
6 Oct 2026, 14:581,904+12
29 Sept 2026, 07:201,892+14
22 Sept 2026, 03:001,878no change
19 Sept 2026, 11:361,878-2
15 Sept 2026, 08:381,880-7
11 Sept 2026, 12:361,887-5
7 Sept 2026, 03:191,892+8
2 Sept 2026, 20:241,884-2
30 Aug 2026, 19:061,886-1
27 Aug 2026, 23:141,887+1
24 Aug 2026, 19:461,886-1
21 Aug 2026, 12:231,887-7
18 Aug 2026, 02:521,894first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 31 October 2026 — this entry's latest reading, not the date you are reading this.

“X_GSM_TEAM_Chat” (@X_GSM_TEAM_CHAT), 1,954 members as measured 31 October 2026. Telegram Register, tgregister.com/channel/X_GSM_TEAM_CHAT.

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.