Telegram RegisterThe public register of Telegram
Telegram profile photo for Павел Швецов | Блог о трафике

Channel

Павел Швецов | Блог о трафике

@pavelprotraffic

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

12,841subscribers

+146 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001552983817
TypeChannel
Username@pavelprotraffic
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 August 2026
Last confirmed live19 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/pavelprotraffic

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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

12,69412,84112,767.57 August 2026 — 12,695 subscribers7 August 2026 — 12,696 subscribers8 August 2026 — 12,694 subscribers9 August 2026 — 12,699 subscribers10 August 2026 — 12,698 subscribers11 August 2026 — 12,705 subscribers12 August 2026 — 12,711 subscribers13 August 2026 — 12,719 subscribers15 August 2026 — 12,726 subscribers16 August 2026 — 12,733 subscribers17 August 2026 — 12,732 subscribers18 August 2026 — 12,735 subscribers19 August 2026 — 12,736 subscribers20 August 2026 — 12,736 subscribers21 August 2026 — 12,744 subscribers23 August 2026 — 12,749 subscribers25 August 2026 — 12,756 subscribers25 August 2026 — 12,765 subscribers26 August 2026 — 12,779 subscribers27 August 2026 — 12,781 subscribers28 August 2026 — 12,775 subscribers30 August 2026 — 12,779 subscribers31 August 2026 — 12,792 subscribers1 September 2026 — 12,797 subscribers2 September 2026 — 12,813 subscribers3 September 2026 — 12,822 subscribers5 September 2026 — 12,821 subscribers8 September 2026 — 12,827 subscribers11 September 2026 — 12,817 subscribers13 September 2026 — 12,808 subscribers15 September 2026 — 12,818 subscribers17 September 2026 — 12,827 subscribers19 September 2026 — 12,841 subscribers7 August 202619 September 2026
33 measurements spanning 43 days, net +146. 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 12,672–12,863 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
19 Sept 2026, 11:4012,841+14
17 Sept 2026, 03:1512,827+9
15 Sept 2026, 01:0012,818+10
13 Sept 2026, 07:3712,808-9
11 Sept 2026, 07:2112,817-10
8 Sept 2026, 10:0112,827+6
5 Sept 2026, 07:1812,821-1
3 Sept 2026, 09:4412,822+9
2 Sept 2026, 01:3812,813+16
1 Sept 2026, 03:5512,797+5
31 Aug 2026, 03:2512,792+13
30 Aug 2026, 02:0712,779+4
28 Aug 2026, 23:4512,775-6
27 Aug 2026, 22:3412,781+2
26 Aug 2026, 20:0312,779+14
25 Aug 2026, 22:5612,765+9
25 Aug 2026, 01:1312,756+7
23 Aug 2026, 12:1212,749+5
21 Aug 2026, 23:3612,744+8
20 Aug 2026, 10:3712,736first reading

Engagement

No public post preview. We read this entry on 20 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.

жиза и арбитраж
@aff_owner · 35,154
Telegram ranks this channel #1 of 57 here — alongside 56 others — read 21 September 2026
PIRATE CPA // Channel
@piratecpa · 28,911
Telegram ranks this channel #1 of 57 here — alongside 56 others — read 9 September 2026
CPALENTA | Арбитраж трафика
@cpa_lenta · 122,026
Telegram ranks this channel #1 of 65 here — alongside 64 others — read 6 September 2026
Partnerkin | Арбитраж трафика
@thepartnerkin · 32,256
Telegram ranks this channel #2 of 66 here — alongside 65 others — read 6 September 2026
Арбитраж трафика с Ивановым
@slovopacana · 163,850
Telegram ranks this channel #19 of 57 here — alongside 56 others — read 21 August 2026
CPA HUNTER | Вакансии арбитража трафика
@hr_affiliate · 34,212
Telegram ranks this channel #27 of 68 here — alongside 67 others — read 6 September 2026
Owner 1win
@owner1w · 24,594
Telegram ranks this channel #36 of 73 here — alongside 72 others — read 15 September 2026
Арбитраж. Все вакансии в одном месте. LENKEP
@Arbitrazh_vakansii_rabota · 27,985
Telegram ranks this channel #45 of 66 here — alongside 65 others — read 10 September 2026
ЖП
@cpalenta · 57,455
Telegram ranks this channel #47 of 71 here — alongside 70 others — read 5 September 2026
R2B.News
@reg2bet · 25,043
Telegram ranks this channel #49 of 75 here — alongside 74 others — read 15 September 2026

This channel appears in 11 seed channels' Telegram-generated recommendation lists in total, of which the 10 where it ranks highest are shown above. 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“Павел Швецов | Блог о трафике” (@pavelprotraffic), 12,841 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/pavelprotraffic.

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.