Telegram RegisterThe public register of Telegram
Telegram profile photo for RAIZEN | Биржа трафика

Supergroup

RAIZEN | Биржа трафика

@traffic_raizen

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

3,471members

+25 since we began measuring on 7 August 2026

217 online right now

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

Register entry

Telegram ID-1002086484241
TypeSupergroup
Username@traffic_raizen
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 September 2026
Last confirmed live4 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/traffic_raizen

Topic

Marketing & affiliate — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

3,4283,4773,452.57 August 2026 — 3,446 members7 August 2026 — 3,445 members10 August 2026 — 3,438 members13 August 2026 — 3,443 members16 August 2026 — 3,459 members19 August 2026 — 3,465 members23 August 2026 — 3,475 members26 August 2026 — 3,472 members29 August 2026 — 3,466 members1 September 2026 — 3,469 members5 September 2026 — 3,468 members8 September 2026 — 3,468 members10 September 2026 — 3,477 members14 September 2026 — 3,469 members18 September 2026 — 3,457 members27 September 2026 — 3,448 members5 October 2026 — 3,438 members12 October 2026 — 3,428 members15 October 2026 — 3,432 members23 October 2026 — 3,440 members27 October 2026 — 3,445 members29 October 2026 — 3,467 members1 November 2026 — 3,464 members4 November 2026 — 3,471 members3,4717 August 20264 November 2026
24 measurements spanning 89 days, net +25. 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 3,421–3,484 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 24
Measured (UTC)MembersChange
4 Nov 2026, 14:363,471+7
1 Nov 2026, 13:393,464-3
29 Oct 2026, 23:303,467+22
27 Oct 2026, 01:093,445+5
23 Oct 2026, 18:303,440+8
15 Oct 2026, 06:313,432+4
12 Oct 2026, 06:203,428-10
5 Oct 2026, 11:183,438-10
27 Sept 2026, 16:583,448-9
18 Sept 2026, 05:163,457-12
14 Sept 2026, 03:583,469-8
10 Sept 2026, 17:203,477+9
8 Sept 2026, 13:353,468no change
5 Sept 2026, 15:183,468-1
1 Sept 2026, 11:353,469+3
29 Aug 2026, 19:133,466-6
26 Aug 2026, 08:553,472-3
23 Aug 2026, 03:133,475+10
19 Aug 2026, 12:063,465+6
16 Aug 2026, 18:223,459first 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 4 November 2026 — this entry's latest reading, not the date you are reading this.

“RAIZEN | Биржа трафика” (@traffic_raizen), 3,471 members as measured 4 November 2026. Telegram Register, tgregister.com/channel/traffic_raizen.

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.