
Supergroup
Арбитраж трафика
@trafic_force
On this record: Growth · Engagement · Cite this entry
7,118members
+151 since we began measuring on 7 August 2026
115 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001066370122 |
|---|---|
| Type | Supergroup |
| Username | @trafic_force |
| Description | Телеграм канал: https://t.me/cpa_cognition Вопросы: @movepawn |
| Created | Between 1 May 2016 and 28 February 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 8 |
| On Telegram | t.me/trafic_force |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 26 Aug 2026, 22:27 | 7,118 | no change |
| 24 Aug 2026, 09:16 | 7,118 | +38 |
| 20 Aug 2026, 18:36 | 7,080 | +55 |
| 17 Aug 2026, 11:28 | 7,025 | +34 |
| 13 Aug 2026, 17:56 | 6,991 | +11 |
| 10 Aug 2026, 19:26 | 6,980 | +19 |
| 7 Aug 2026, 18:30 | 6,961 | -6 |
| 7 Aug 2026, 05:05 | 6,967 | first 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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“Арбитраж трафика” (@trafic_force), 7,118 members as measured 26 August 2026. Telegram Register, tgregister.com/channel/trafic_force.
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.