Channel
Переходилки
@perexodvtak2
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,408subscribers
-54 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001215867534 |
|---|---|
| Type | Channel |
| Username | @perexodvtak2 |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 2 times, most recently 6 November 2026 |
| On Telegram | t.me/perexodvtak2 |
Topic
Other / unclassifiable — 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 97% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 07:29 | 3,408 | -2 |
| 28 Oct 2026, 06:47 | 3,410 | -2 |
| 18 Oct 2026, 20:01 | 3,412 | -1 |
| 12 Oct 2026, 11:19 | 3,413 | -2 |
| 6 Oct 2026, 00:01 | 3,415 | -6 |
| 28 Sept 2026, 14:01 | 3,421 | -15 |
| 15 Sept 2026, 19:57 | 3,436 | -1 |
| 12 Sept 2026, 06:00 | 3,437 | -6 |
| 8 Sept 2026, 20:06 | 3,443 | no change |
| 8 Sept 2026, 03:37 | 3,443 | -4 |
| 30 Aug 2026, 20:59 | 3,447 | -5 |
| 27 Aug 2026, 11:18 | 3,452 | -2 |
| 24 Aug 2026, 19:19 | 3,454 | +2 |
| 20 Aug 2026, 20:33 | 3,452 | -2 |
| 17 Aug 2026, 18:16 | 3,454 | -2 |
| 14 Aug 2026, 17:57 | 3,456 | +1 |
| 10 Aug 2026, 22:31 | 3,455 | -6 |
| 8 Aug 2026, 04:04 | 3,461 | -1 |
| 7 Aug 2026, 11:22 | 3,462 | 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.
@perexodvtak · 96,600
Telegram ranks this channel #4 of 92 here — alongside 91 others — read 16 August 2026
@prostovtak · 25,178
Telegram ranks this channel #5 of 94 here — alongside 93 others — read 14 September 2026
@tushevskaia · 22,701
Telegram ranks this channel #17 of 96 here — alongside 95 others — read 19 September 2026
@AgeofAquariusuncensored · 28,160
Telegram ranks this channel #72 of 95 here — alongside 94 others — read 9 September 2026
This channel appears in 4 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“Переходилки” (@perexodvtak2), 3,408 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/perexodvtak2.
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.