Telegram RegisterThe public register of Telegram
Telegram profile photo for TOR REBORN

Channel

TOR REBORN

@Tor_Portable

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

8,204subscribers

+595 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003002719766
TypeChannel
Username@Tor_Portable
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/Tor_Portable

Growth

7,6098,2047,906.56 August 2026 — 7,609 subscribers7 August 2026 — 7,615 subscribers10 August 2026 — 7,631 subscribers13 August 2026 — 7,647 subscribers16 August 2026 — 7,684 subscribers20 August 2026 — 7,717 subscribers23 August 2026 — 7,745 subscribers26 August 2026 — 7,790 subscribers28 August 2026 — 7,851 subscribers1 September 2026 — 7,906 subscribers4 September 2026 — 8,070 subscribers10 September 2026 — 8,204 subscribers6 August 202610 September 2026
12 measurements spanning 35 days, net +595. 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 7,520–8,293 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 03:398,204+134
4 Sept 2026, 21:178,070+164
1 Sept 2026, 04:267,906+55
28 Aug 2026, 23:257,851+61
26 Aug 2026, 07:427,790+45
23 Aug 2026, 05:547,745+28
20 Aug 2026, 00:027,717+33
16 Aug 2026, 16:437,684+37
13 Aug 2026, 02:167,647+16
10 Aug 2026, 05:257,631+16
7 Aug 2026, 08:077,615+6
6 Aug 2026, 15:317,609first reading

Engagement

63 posts held, back to 26 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 18 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
36.9%
avg views ÷ 8,204 subscribers
Avg views / post
3,020
44 posts measured
Reaction rate
1.67%
reactions ÷ views · ER floor
Posts in window
44
of 63 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 August 2026
Posts held63 (26 July 202628 August 2026)
Views total133,020
Reactions total2,224
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 20:35 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
55s
Average length
28s

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

3,915 reactions across 63 posts, in 49 distinct kinds. The most used accounts for 26.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁1,02426.2%
65516.7%
👍51813.2%
🤡3358.56%
🤣3127.97%
🔥2396.10%
😭1553.96%
🫡1072.73%
😢1002.55%
👀882.25%
❤‍🔥541.38%
👎421.07%
👏411.05%
🙏280.715%
💘250.639%
🤮230.587%
💩160.409%
🤔160.409%
🐳150.383%
🕊150.383%
29 further kinds1072.73%

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

Measured over the 63 most recent posts we hold, published 26 July 2026 to 28 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

28 Aug 2026, 17:55 UTC≈1,050 views32 reactionsread 28 August 2026
Photo

Новый Xray У основного ядра для обхода цензуры появилась большая проблема. Это неистовый консерватизм и отказ от всего нового. Идеи требующие срочного решения часто неаргументированно закрываются одним из модераторов проекта, который должен следить за его чистотой и качеством. Например им чуть не были загублены поправки в код транспорта xhttp, пока не пришёл главный администратор RPRX и не уладил всё, сделав его кон

👍25🤡61

26 Aug 2026, 19:47 UTC≈2,320 views7 reactionsread 28 August 2026
File

Для всяких умников из комментариев:

7

26 Aug 2026, 16:21 UTC≈2,450 views27 reactionsread 28 August 2026

Сегодня в первый раз столкнулся с перехватом DNS на сервере WBM. Из-за этого пинги не долетали и шли таймауты. Об этом же я писал 24 августа но тогда не было выяснено что корневая причина — перехват DNS на белых серверах. ИИ вероятно ошибся в анализе и временное облегчение принял за результат работы. Любят российские сервера перехватывать DNS что для VPN смерти подобно. Проблема исправлена.

22🙏3🤬2

26 Aug 2026, 14:40 UTC≈2,270 views56 reactionsread 28 August 2026

ЗАМЕТКИ ПО МЕХАНИЗМУ БЛОКИРОВОК В РОССИИ Ранее я говорил, что основной механизм, которым Роскомнадзор блокирует VPN — адрес конечной точки. Поэтому если скрыть конечную точку через мостовое туннелирование, также называемое каскадом, проблема перестанет быть значительной. К сожалению, это не так. По закону о суверенном Интернете 2019 года ТСПУ стоит на каждом российском сервере. В разных местах он настроен в разных

👍3512😁4🤡2🤮2🙈1

25 Aug 2026, 13:27 UTC≈2,880 views190 reactionsread 28 August 2026

С сегодняшнего дня создал зеркало канала в приложении MAX, прошу подписываться! 🥳 https://max.ru/Tor_Portable

🤣81😭54🤡20🙏9😁74🌚4💊4

24 Aug 2026, 18:57 UTC≈3,050 views40 reactionsread 28 August 2026

В их результате было получено точное знание о том, что Убунту — худший линукс-дистрибутив из всех, и он одним своим существованием кладёт сервера. Слава Богу что среди всех моих машин лишь на одной по несчастью была Убунту.

😭22🤔65🤡2😁2👏1💋1🔥1

24 Aug 2026, 18:53 UTC≈2,940 views30 reactionsread 28 August 2026

Дней без тех. работ по самым критически важным серверам: 0

👀22😁7💋1

23 Aug 2026, 20:13 UTC≈3,380 views65 reactionsread 28 August 2026
Photo

Прошло 10 минут с момента выхода поста, вы не поверите

😁60🔥3🌚1😐1

23 Aug 2026, 20:00 UTC≈3,300 views11 reactionsread 28 August 2026

КАК ОПЛАЧИВАТЬ? Участились жалобы на медленную работу СБП. Ребята, разные платёжные провайдеры работают по-разному! Если за одну минуту не пришла оплата, не паникуйте. У нынешнего провайдера СБП низкие комиссии, но они работают довольно медленно. Баланс на счёт приходит через ~10 минут, бывало раньше что и час на это тратился, потом я кое-что донастроил и теперь всё упирается в 10 минут максимум. Кому-то и этого мн

😁11

23 Aug 2026, 18:22 UTC≈3,100 views77 reactionsread 28 August 2026
Video

Video, posted without a caption

😁68👏6🎉2💋1

22 Aug 2026, 23:48 UTC≈3,520 views32 reactionsread 28 August 2026
Photo

Инспекция белых серверов @RebornVPN_Bot на качество в @bschekbot: Всего в наличии есть 4 белых сервера плюс отбеленная подписка (получить сервера можно в белых же условиях). 14 из 15 операторов рекомендуют!!! Самый лучший чекер @bschekbot вернулся в строй лучше чем прежде! 1) Сервер WHITE BOSS NINJA. 10 из 15. Сервер — ходячий труп, намертво держащийся на уже заблокированном подключении. Когда-то был полным униве

🔥234🤡4😍1

22 Aug 2026, 21:16 UTC≈3,230 views55 reactionsread 28 August 2026

Сегодня в первый раз вернул деньги человеку. Когда у меня запрашивают возврат средств — моя главная цель удостовериться, что я сделал всё возможное для восстановления работоспособности. Да, такое уже бывало, но едва-едва удавалось не доводить до края, и это важно! Должна быть уважительная причина, необходимо быть лучшим, а если ты вернул деньги, ты признал свою нерыночность, неконкурентоспособность. В этот раз об

💘2516😁4👍3🔥3🤡2💋1💩1

Showing the 12 most recent of 63 posts we hold for @Tor_Portable. 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 2 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 10 September 2026 — this entry's latest reading, not the date you are reading this.

“TOR REBORN” (@Tor_Portable), 8,204 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/Tor_Portable.

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.