Telegram RegisterThe public register of Telegram
Telegram profile photo for REKTOR ⚔️ РЕКТОР

Channel

REKTOR ⚔️ РЕКТОР

@rektor_7

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

1,134subscribers

-5 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-1002004998564
TypeChannel
Username@rektor_7
Created4 November 2023measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live29 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/rektor_7

Growth

1,1341,1391,136.57 August 2026 — 1,139 subscribers7 August 2026 — 1,139 subscribers10 August 2026 — 1,138 subscribers13 August 2026 — 1,137 subscribers16 August 2026 — 1,136 subscribers22 August 2026 — 1,135 subscribers29 August 2026 — 1,134 subscribers7 August 202629 August 2026
7 measurements spanning 22 days, net -5. 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,133–1,140 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 11:381,134-1
22 Aug 2026, 20:221,135-1
16 Aug 2026, 16:041,136-1
13 Aug 2026, 07:151,137-1
10 Aug 2026, 16:341,138-1
7 Aug 2026, 23:481,139no change
7 Aug 2026, 14:211,139first reading

Engagement

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

What this channel posts

Video runtime
19m 57s
Average length
6m 39s

Measured directly from 3 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

1,211 reactions across 16 posts, in 17 distinct kinds. The most used accounts for 39.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
48139.7%
👍35929.6%
🔥1119.17%
😁715.86%
😢473.88%
🫡342.81%
🤬282.31%
custom 5425076476951141962201.65%
🥰151.24%
🤔141.16%
👏80.661%
🤷‍♂70.578%
custom 533938828021335968760.495%
😱40.33%
🤯30.248%
custom 534130077761066327820.165%
🏆10.083%

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 areTelegram’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 16 of the 18 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 1,211reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 4 November 2023 to 15 February 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

15 Feb 2026, 13:33 UTC690 views36 reactionsread 7 August 2026
Photo

⚔️Битва между РКН и Telegram. Наверняка только ленивый не прокомментировал замедление в России Telegram, буду краток, когда мы прекратим "стрелять себя по ногам" ? Я в а**е😡 Когда то первым выстрелом был Discord. (по мнению Роскомнадзора, Discord использовался в террористических и экстремистских целях)

🤬26custom 53393882802133596876🤷‍♂3🤔1

14 Feb 2026, 15:48 UTC688 views42 reactionsread 7 August 2026
Photo

С днём всех влюблённых❤️ Мои мир, моя жизнь ❤️

30👍11🤬1

4 Jan 2026, 16:20 UTC≈1,130 views96 reactionsread 7 August 2026
Photo

Всех с Новым годом друзья ❗️ Друзья, меня давно не было на связи, связано это с тем, что служба занимала 100% времени, за этот год в моей жизни произошли изменения, со мной все в порядке, я все так же на СВО, хоть и спицифика моей работы сильно изменилась. Спасибо всем кто остался тут, обнял поднял. Буду стараться не теряться🫡 😇@rektorZV😇

63👍18🫡11🥰2👏1custom 54250764769511419621

21 Mar 2025, 15:45 UTC≈4,220 views134 reactionsread 7 August 2026

Стоматологи - это врачи которые дарят настроение, после адской зубной боли, выходя от стоматолога, настроение прекрасное. Когда зубы не болят это кайф 😌

😁67👍4417🔥5🤷‍♂1

21 Mar 2025, 13:45 UTC≈4,000 views87 reactionsread 7 August 2026
Photo

😭

😢4119🫡10🥰7😱4👍3🤯3

21 Mar 2025, 13:02 UTC≈3,310 views72 reactionsread 7 August 2026
Photo

Мариуполь

👍5711custom 54250764769511419624

20 Mar 2025, 05:55 UTC≈2,860 views84 reactionsread 7 August 2026
Video

ФСБ предотвратила теракт в Мариуполе: задержан местный житель

👍73custom 54250764769511419626👏5

19 Mar 2025, 14:31 UTC≈2,640 views99 reactionsread 7 August 2026
Video

Путь ЧВК "Вагнер" в СВО😇😇

🔥6217👍16👏2custom 53413007776106632782

19 Mar 2025, 14:14 UTC≈2,340 views117 reactionsread 7 August 2026
Photo

3 года назад, 19 марта 2022 года, ЧВК Вагнер начал свои путь в зоне СВО.😇😇

87👍18🫡8custom 54250764769511419623🏆1

19 Mar 2025, 13:09 UTC≈1,710 views48 reactionsread 7 August 2026
Photo

Защита шеи ( кевлар) + бронежилет ( кокон / блиты 4бр / балистика ) = Неподвижный солдат. Смотрится вроде симпатично , но не практично❗️

31🤔13🤷‍♂3custom 54250764769511419621

19 Mar 2025, 05:09 UTC≈1,480 views69 reactionsread 7 August 2026

Доброе утро друзья🫡 Всем хорошего дня😇

49👍19custom 54250764769511419621

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

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

“REKTOR ⚔️ РЕКТОР” (@rektor_7), 1,134 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/rektor_7.

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.