Telegram RegisterThe public register of Telegram
Telegram profile photo for REDEXGAME | ردکس گیم

Channel

REDEXGAME | ردکس گیم

@redexgame

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

2,604subscribers

+2,590 since we began measuring on 3 October 2026

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

Register entry

Telegram ID-1001594736043
TypeChannel
Username@redexgame
Created12 November 2021 — measured — dated from the channel’s first post
First recorded3 October 2026
Last confirmed live17 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/redexgame

Topic

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

142,6041,3093 October 2026 — 14 subscribers3 October 2026 — 14 subscribers15 October 2026 — 919 subscribers21 October 2026 — 1,932 subscribers24 October 2026 — 1,979 subscribers27 October 2026 — 1,998 subscribers29 October 2026 — 2,010 subscribers1 November 2026 — 2,067 subscribers4 November 2026 — 2,244 subscribers8 November 2026 — 2,335 subscribers12 November 2026 — 2,463 subscribers17 November 2026 — 2,604 subscribers3 October 202617 November 2026
12 measurements spanning 45 days, net +2,590. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Nov 2026, 07:462,604+141
12 Nov 2026, 06:292,463+128
8 Nov 2026, 02:212,335+91
4 Nov 2026, 23:392,244+177
1 Nov 2026, 13:392,067+57
29 Oct 2026, 19:112,010+12
27 Oct 2026, 03:191,998+19
24 Oct 2026, 03:451,979+47
21 Oct 2026, 10:191,932+1,013
15 Oct 2026, 08:59919+905
3 Oct 2026, 07:2214no change
3 Oct 2026, 06:4814first reading

Engagement

1 post held, back to 12 November 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 1 post for this entry, the most recent from 12 November 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 1 most recent of 1 post we hold for @redexgame. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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.

“REDEXGAME | ردکس گیم” (@redexgame), 2,604 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/redexgame.

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.