Channel
affy | CPA courses | Арбитраж трафика курсы, обучение, новичку
@affy_arbitrazh_trafika_kursy
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,984subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001482366266 |
|---|---|
| Type | Channel |
| Username | @affy_arbitrazh_trafika_kursy |
| Description | Лучшие бесплатные курсы по арбитражу трафика, а также эффективное обучение арбитражу трафика для новичков. все материалы были взяты из открытых источников - если вы хотите удалить свой курс пишите на @affy_support |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 21 September 2026 |
| Measurements held | 12 |
| On Telegram | t.me/affy_arbitrazh_trafika_kursy |
Topic
Education — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Sept 2026, 01:45 | 1,984 | no change |
| 18 Sept 2026, 20:15 | 1,984 | -6 |
| 14 Sept 2026, 03:18 | 1,990 | -1 |
| 10 Sept 2026, 09:15 | 1,991 | +5 |
| 5 Sept 2026, 04:57 | 1,986 | -5 |
| 1 Sept 2026, 09:05 | 1,991 | -1 |
| 29 Aug 2026, 07:44 | 1,992 | +6 |
| 26 Aug 2026, 12:23 | 1,986 | -1 |
| 23 Aug 2026, 07:55 | 1,987 | -3 |
| 19 Aug 2026, 17:13 | 1,990 | +4 |
| 7 Aug 2026, 14:52 | 1,986 | -1 |
| 7 Aug 2026, 04:37 | 1,987 | 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@Arbitrazh_vakansii_rabota · 27,985
Telegram ranks this channel #29 of 66 here — alongside 65 others — read 10 September 2026
@hr_affiliate · 34,347
Telegram ranks this channel #44 of 68 here — alongside 67 others — read 6 September 2026
@works_cpa · 20,656
Telegram ranks this channel #62 of 79 here — alongside 78 others — read 26 September 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 21 September 2026 — this entry's latest reading, not the date you are reading this.
“affy | CPA courses | Арбитраж трафика курсы, обучение, новичку” (@affy_arbitrazh_trafika_kursy), 1,984 subscribers as measured 21 September 2026. Telegram Register, tgregister.com/channel/affy_arbitrazh_trafika_kursy.
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.