Telegram RegisterThe public register of Telegram
Telegram profile photo for 134 причины | Ротор

Channel

134 причины | Ротор

@rotor134reasons

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

1,188subscribers

-11 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-1002376567421
TypeChannel
Username@rotor134reasons
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/rotor134reasons

Topic

Sports — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

1,1861,2031,194.56 August 2026 — 1,199 subscribers6 August 2026 — 1,199 subscribers9 August 2026 — 1,198 subscribers13 August 2026 — 1,203 subscribers19 August 2026 — 1,201 subscribers23 August 2026 — 1,202 subscribers25 August 2026 — 1,195 subscribers29 August 2026 — 1,194 subscribers1 September 2026 — 1,192 subscribers4 September 2026 — 1,191 subscribers10 September 2026 — 1,190 subscribers13 September 2026 — 1,186 subscribers18 September 2026 — 1,188 subscribers1,1886 August 202618 September 2026
13 measurements spanning 43 days, net -11. 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,183–1,206 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 05:211,188+2
13 Sept 2026, 17:361,186-4
10 Sept 2026, 00:171,190-1
4 Sept 2026, 18:211,191-1
1 Sept 2026, 05:131,192-2
29 Aug 2026, 04:581,194-1
25 Aug 2026, 22:081,195-7
23 Aug 2026, 03:051,202+1
19 Aug 2026, 18:421,201-2
13 Aug 2026, 03:051,203+5
9 Aug 2026, 17:011,198-1
6 Aug 2026, 17:301,199no change
6 Aug 2026, 14:041,199first reading

Engagement

20 posts held, back to 29 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

246 reactions across 18 posts, in 12 distinct kinds. The most used accounts for 24.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍6024.4%
🤣6024.4%
5522.4%
🔥239.35%
😁135.28%
👎124.88%
custom 546064475469174618772.85%
😭62.44%
custom 533721906403083423441.63%
🤡31.22%
custom 521754497146843627920.813%
🍾10.407%

Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 18 of the 20 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 246 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 29 July 2026 to 6 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.

Telegram Stars

Stars received
5
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @rotor134reasons. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 29 July 2026 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Aug 2026, 11:51 UTC209 views22 reactionsread 6 August 2026
Photo

Ёжик может пополнить состав волгоградского «Ротора» По моей информации, молодой игрок из Ромашковой долины сейчас рассматривается в качестве правого защитника в ротацию к Георгию Юдинцеву. Воспитанник петербургского футбола проводил переговоры с другим клубом Лиги PARI — «Ленинградцем», местным гегемоном из Рощино, но выбрал команду Парфёнова. Осталось дело за малым — приехать в Волгоград и подписать контракт. @r

🤣15custom 54606447546917461876🍾1

6 Aug 2026, 05:28 UTC353 views9 reactionsread 6 August 2026
File

БОЯРИКИ#3 В гостях — Алина, автор тг-канала Манеж Енисея 1:08 — ориджин Алины 2:46 — создание тг-канала про «Енисей» 5:59 — как начался канал «134 причины» 6:18 — рождение канала «Время Родины» 7:20 — переименование в «Манеж Енисея» 8:52 — кто помогал Алине 10:35 — респект ФКРВ Суппортерс 11:20 — общение с футболистами «Енисея» 12:54 — мнение окружения о том, что ты блогер 14:01 — платят ли авторам тг-каналов деньг

👍6🔥21

4 Aug 2026, 06:28 UTC311 views7 reactionsread 6 August 2026
Photo

Немного продвинутой статистики после матча 4-го тура Лиги PARI «Велес» — «Ротор». Голевые ошибки РУСТАТ считает, что их было 3. Привезли Поярков, Юдинцев и Данилкин. Голевые моменты «Ротор» создал всего 1 голевой момент: Симонян вырезал на Эльдарушева, а дальше вы всё видели. Прогрессивные передачи Больше всех мяч вперёд двигал Умников — 18 передач (39% точности). Чуть меньше: Поярков — 14 (71% точности), Аюпов — 16

👍6🔥1

3 Aug 2026, 19:55 UTC368 views27 reactionsread 6 August 2026
Photo

Он что-то знал...

🤣25custom 52175449714684362792

3 Aug 2026, 19:00 UTC382 viewsread 6 August 2026

Лучший и худший игрок в составе 💙

3 Aug 2026, 18:29 UTC395 views6 reactionsread 6 August 2026

Стукалов перевернул игру, а «Велес» гнул свою линию и заслуженно камбэкнул. С этим «Велесом» всем будет неудобно. После выхода трио Родионов-Хубулов-Хохлачёв как будто исчезла вся магия. Ну и после этой игры, МОЖЕТ БЫТЬ, станет очевидно, что НУЖЕН еще один ПРОФИЛЬНЫЙ ПРАВЫЙ ЗАЩИТНИК. А как Храмцов долго вводил аут — отдельная песня. Наверное, такое бывает, когда порядок бьёт класс. Сегодня во втором тайме было именн

😭6

3 Aug 2026, 17:23 UTC388 views9 reactionsread 6 August 2026

Такой добротный матч Лиги PARI: много борьбы и стыков. «Велес» удивил своей тройкой, хотя матч с «Енисеем» они тоже заканчивали по такой схеме. Неплохо выбегали в контратаки, но пока, слава богу, безрезультатно. Эмик — скала. Поярков — зверь. Сима — бой. Абу-Саид — гол. @rotor134reasons

🔥9

3 Aug 2026, 15:37 UTC403 views15 reactionsread 6 August 2026
Video

Книги, изменившие мир. Писатели, объединившие поколения. 📺«Уфа» - «КАМАЗ» Лига PARI. 4 тур. @rotor134reasons

😁11👍2🔥2

3 Aug 2026, 10:07 UTC350 views2 reactionsread 6 August 2026

Я-то думал, вам нравятся разные рубрики на канале, посвящённые Лиге, в которой играет «Ротор» Как же я ошибался🥺

👍2

3 Aug 2026, 09:55 UTC342 views49 reactionsread 6 August 2026

Скучаете по «Вестнику Лиги PARI»? ❤️— Да 👎 — Нет @rotor134reasons

28👎12custom 53372190640308342344🔥2🤣2custom 54606447546917461871

Showing the 12 most recent of 20 posts we hold for @rotor134reasons. 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

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.

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

“134 причины | Ротор” (@rotor134reasons), 1,188 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/rotor134reasons.

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.