Telegram RegisterThe public register of Telegram
Telegram profile photo for RIOT 社区

Supergroup

RIOT 社区

@riotcall

Has discussion group

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

2,258members

+76 since we began measuring on 7 August 2026

65 online right now

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

Register entry

Telegram ID-1001199618653
TypeSupergroup
Username@riotcall
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 September 2026
Last confirmed live18 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/riotcall

Topic

Crypto & trading — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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

2,1802,2582,2197 August 2026 — 2,182 members7 August 2026 — 2,180 members10 August 2026 — 2,193 members14 August 2026 — 2,216 members17 August 2026 — 2,214 members20 August 2026 — 2,217 members24 August 2026 — 2,224 members27 August 2026 — 2,231 members30 August 2026 — 2,215 members2 September 2026 — 2,211 members5 September 2026 — 2,201 members10 September 2026 — 2,193 members14 September 2026 — 2,228 members18 September 2026 — 2,228 members18 September 2026 — 2,258 members7 August 202618 September 2026
15 measurements spanning 42 days, net +76. 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 2,168–2,270 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
18 Sept 2026, 14:382,258+30
18 Sept 2026, 02:252,228no change
14 Sept 2026, 08:552,228+35
10 Sept 2026, 19:412,193-8
5 Sept 2026, 22:382,201-10
2 Sept 2026, 04:072,211-4
30 Aug 2026, 08:462,215-16
27 Aug 2026, 02:042,231+7
24 Aug 2026, 08:182,224+7
20 Aug 2026, 18:442,217+3
17 Aug 2026, 16:072,214-2
14 Aug 2026, 09:152,216+23
10 Aug 2026, 15:522,193+13
7 Aug 2026, 18:322,180-2
7 Aug 2026, 10:412,182first 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.

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.

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

“RIOT 社区” (@riotcall), 2,258 members as measured 18 September 2026. Telegram Register, tgregister.com/channel/riotcall.

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.