Telegram RegisterThe public register of Telegram
Telegram profile photo for RPS League - Grupo Oficial Español 🇪🇸

Supergroup

RPS League - Grupo Oficial Español 🇪🇸

@rpsleaguenft_ESP

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

1,288members

-53 since we began measuring on 7 August 2026

47 online right now

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

Register entry

Telegram ID-1001661453554
TypeSupergroup
Username@rpsleaguenft_ESP
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 October 2026
Last confirmed live17 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/rpsleaguenft_ESP

Topic

Gaming — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 58% 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,2881,3411,314.57 August 2026 — 1,341 members14 August 2026 — 1,338 members17 August 2026 — 1,335 members20 August 2026 — 1,334 members24 August 2026 — 1,333 members27 August 2026 — 1,332 members30 August 2026 — 1,330 members2 September 2026 — 1,325 members8 September 2026 — 1,319 members12 September 2026 — 1,318 members15 September 2026 — 1,317 members26 September 2026 — 1,314 members1 October 2026 — 1,314 members5 October 2026 — 1,312 members11 October 2026 — 1,310 members14 October 2026 — 1,307 members18 October 2026 — 1,304 members24 October 2026 — 1,303 members27 October 2026 — 1,301 members30 October 2026 — 1,297 members2 November 2026 — 1,296 members12 November 2026 — 1,294 members17 November 2026 — 1,288 members7 August 202617 November 2026
23 measurements spanning 103 days, net -53. 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,280–1,349 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 23
Measured (UTC)MembersChange
17 Nov 2026, 20:361,288-6
12 Nov 2026, 22:561,294-2
2 Nov 2026, 17:591,296-1
30 Oct 2026, 12:471,297-4
27 Oct 2026, 03:371,301-2
24 Oct 2026, 01:211,303-1
18 Oct 2026, 01:191,304-3
14 Oct 2026, 19:571,307-3
11 Oct 2026, 07:211,310-2
5 Oct 2026, 09:011,312-2
1 Oct 2026, 23:491,314no change
26 Sept 2026, 21:151,314-3
15 Sept 2026, 23:591,317-1
12 Sept 2026, 15:371,318-1
8 Sept 2026, 09:581,319-6
2 Sept 2026, 20:551,325-5
30 Aug 2026, 11:531,330-2
27 Aug 2026, 10:081,332-1
24 Aug 2026, 17:241,333-1
20 Aug 2026, 16:151,334first 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 17 November 2026 — this entry's latest reading, not the date you are reading this.

“RPS League - Grupo Oficial Español 🇪🇸” (@rpsleaguenft_ESP), 1,288 members as measured 17 November 2026. Telegram Register, tgregister.com/channel/rpsleaguenft_ESP.

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.