Telegram RegisterThe public register of Telegram
Telegram profile photo for Передвач

Channel

Передвач

@peredva4

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,837subscribers

+59 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001160271815
TypeChannel
Username@peredva4
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/peredva4

Growth

1,7781,8591,818.56 August 2026 — 1,778 subscribers6 August 2026 — 1,778 subscribers9 August 2026 — 1,791 subscribers12 August 2026 — 1,810 subscribers15 August 2026 — 1,859 subscribers18 August 2026 — 1,850 subscribers21 August 2026 — 1,842 subscribers24 August 2026 — 1,835 subscribers28 August 2026 — 1,832 subscribers31 August 2026 — 1,835 subscribers4 September 2026 — 1,837 subscribers1,8376 August 20264 September 2026
11 measurements spanning 29 days, net +59. 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 1,766–1,871 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 04:001,837+2
31 Aug 2026, 13:581,835+3
28 Aug 2026, 03:531,832-3
24 Aug 2026, 17:161,835-7
21 Aug 2026, 11:031,842-8
18 Aug 2026, 04:321,850-9
15 Aug 2026, 10:431,859+49
12 Aug 2026, 04:421,810+19
9 Aug 2026, 06:471,791+13
6 Aug 2026, 07:011,778no change
6 Aug 2026, 01:501,778first reading

Engagement

31 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 31 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
52s
Average length
10s

Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

336 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 31.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣10731.8%
9327.7%
😁8725.9%
👎133.87%
🔥113.27%
😭82.38%
👏61.79%
🖕41.19%
🤮30.893%
🤝20.595%
👍10.298%
🤯10.298%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 29 of the 31 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 661 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 31 most recent posts we hold, published 4 August 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 14:20 UTC270 views1 reactionsread 7 August 2026
Forwarded from @srochnosport

❗️ «Расинг» отклонил первое предложение ЦСКА по трансферу правого защитника Гастона Мартирены, сообщил Sport24 источник, знакомый с ситуацией. «Аргентинский клуб не заинтересован во включении Рамиро Ди Лусиано в сделку и рассчитывает получить денежную компенсацию за полноценный трансфер Мартирены. После отклонения первого предложения новых контактов со стороны ЦСКА не было, как и второго предложения», — отмечает ист

1

7 Aug 2026, 12:37 UTC407 views14 reactionsread 7 August 2026
Photo

Голосуем за Семака в сентябре. 🐻 @peredva4

😁14

7 Aug 2026, 08:32 UTC483 views11 reactionsread 7 August 2026
Video

Оператор — Роман Юрьевич. 🐻 @peredva4

6🤣5

7 Aug 2026, 08:04 UTC496 views9 reactionsread 7 August 2026
Photo

Мало кто знает, но даже тут Шевелев в последний момент слился с переговоров. 🐻 @peredva4

9

6 Aug 2026, 21:22 UTC609 views22 reactionsread 7 August 2026
Photo

Назовите мне хотя бы одну разумную причину, из-за которой вы все забыли этого человека. 🐻 @peredva4

11🤣9🤮2

6 Aug 2026, 16:16 UTC626 views18 reactionsread 7 August 2026
Photo

• 4:19: • 4:20: 🐻 @peredva4

🤣18

6 Aug 2026, 15:54 UTC613 views13 reactionsread 7 August 2026
Video

Он ведь и этот трансфер до конца не доведёт. 🐻 @peredva4

😁13

6 Aug 2026, 15:21 UTC313 views5 reactionsread 7 August 2026
Forwarded from @offsiderPhoto

Сразу несколько клубов РПЛ заинтересованы в аренде нападающего ЦСКА Тамерлана Мусаева. По нашей информации среди возможных вариантов «Рубин», «Ростов» и махачкалинское «Динамо». По словам источников армейцы будут готовы отпустить Мусаева в аренду, если удастся приобрести еще одного нападающего. У армейцев в составе уже есть Воронов и Гонду и, в случае усиления состава у Мусаева игровой практики, вероятно, станет мен

3🤝2

6 Aug 2026, 09:23 UTC599 views35 reactionsread 7 August 2026
Photo

Мирлинд Даку, мой любимый Мирлинд Даку. Он снова не игрок ЦСКА. Он снова переходит в другой клуб РПЛ. Очень жаль по-человечески. Даже админы тг-каналов, они не должны быть нейтральными. Это судьи должны быть нейтральными. Админы каналов всё же люди. И у них тоже есть симпатии. Я клянусь вам, я очень хотел, чтобы Мирлинд Даку стал красно-синим. 🐻 @peredva4

😁22😭8🖕4🤮1

6 Aug 2026, 07:11 UTC480 viewsread 7 August 2026
Forwarded from @CSKAbyMikePhoto

🎁 РОЗЫГРЫШ ИГРОВОЙ ФОРМЫ ЦСКА 2026/27! Хотите получить новую игровую форму ЦСКА сезона 2026/27? Тогда участвуйте в нашем розыгрыше! 🔥 🏆 Приз: • 1 победитель • Игровая форма ЦСКА со всеми спонсорами на выбор — домашняя или выездная. 📋 Условия участия: 1️⃣ Подписаться на все 5 каналов-спонсоров: • Армейский дух | ЦСКА • ПеРо о ЦСКА • CSKA by Mike • Вокруг да около российского футбола • Удар Эджуке | ЦСКА 2️⃣ Нажат

5 Aug 2026, 21:12 UTC635 views5 reactionsread 7 August 2026
Photo

🌍 | Худяков продолжает свой путь к основному этапу Лиги Чемпионов. Время вернуть рубрику о наших ребятах зарубежом. Благо, есть за кем следить. Скоро стартуют сезоны в основных чемпионатах, а пока — квалификация еврокубков. «Штурм» — ещё в деле. Планируют как минимум повторить успех прошлого сезона, но для этого нужно переигрывать турков в ответном матче. Сегодня же — гостевое поражение 0:2. 🟢 Статистика Даниила:

🔥5

Showing the 12 most recent of 31 posts we hold for @peredva4. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

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 10 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.

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 September 2026 — this entry's latest reading, not the date you are reading this.

“Передвач” (@peredva4), 1,837 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/peredva4.

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.