Technology — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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
26 measurements spanning 96 days, net +860. 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,456–8,783 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)
Subscribers
Change
10 Nov 2026, 06:26
8,469
-5
6 Nov 2026, 19:39
8,474
-9
3 Nov 2026, 13:37
8,483
-13
31 Oct 2026, 05:20
8,496
-18
28 Oct 2026, 12:08
8,514
-25
25 Oct 2026, 03:28
8,539
-26
22 Oct 2026, 06:01
8,565
-41
18 Oct 2026, 15:35
8,606
-24
15 Oct 2026, 09:15
8,630
+108
11 Oct 2026, 23:41
8,522
-23
5 Oct 2026, 03:37
8,545
+172
26 Sept 2026, 15:18
8,373
-188
17 Sept 2026, 23:15
8,561
+260
14 Sept 2026, 04:18
8,301
+97
10 Sept 2026, 03:39
8,204
+134
4 Sept 2026, 21:17
8,070
+164
1 Sept 2026, 04:26
7,906
+55
28 Aug 2026, 23:25
7,851
+61
26 Aug 2026, 07:42
7,790
+45
23 Aug 2026, 05:54
7,745
first reading
Engagement
96 posts held, back to 26 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 35 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
38.9%
avg views ÷ 8,469 subscribers
Avg views / post
3,300
33 posts measured
Reaction rate
1.57%
reactions ÷ views · ER floor
Posts in window
33
of 96 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. It is computed over the 32 of 33 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 November 2026
Posts held
96 (26 July 2026 – 7 November 2026)
Views total
108,740
Reactions total
1,672
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 13:08 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
Photos
376
Videos
10
Links
126
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
2m 03s
Average length
31s
Measured directly from 4 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
5,587 reactions across 95 posts, in 56 distinct kinds. The most used accounts for 24.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
1,339
24.0%
😁
1,195
21.4%
👍
630
11.3%
🤡
442
7.91%
🔥
389
6.96%
🤣
344
6.16%
😭
216
3.87%
❤🔥
138
2.47%
🫡
107
1.92%
👏
106
1.90%
😢
106
1.90%
👀
96
1.72%
👎
63
1.13%
🤔
49
0.877%
💯
47
0.841%
🙏
29
0.519%
👌
28
0.501%
💘
25
0.447%
🤮
23
0.412%
💩
19
0.34%
36 further kinds
196
3.51%
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 95 of the 96 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 5,587 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 96 most recent posts we hold, published 26 July 2026 to 7 November 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
Telegram’s own ‘edited’ marker: 7 of 33 posts held from the last 30 days (21.2%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
У моего любимого приложения Throne вышел собственный Telegram канал
https://t.me/ThroneProj
Я являюсь лояльным юзером Throne с 2024 года, под капотом это буквально тот же Хапп, но гораздо более адекватно сделанный, с неисчислимым количеством функций, более нормально реализованных (больше протоколов, лучше туннелирование, лучше интерфейс, лучше всё, открытый код).
Разработчик ведёт себя профессионально, на вайбкод …
Завершил диагностику бесплатного сервера, больших проблем не выявили, включил его снова. Если проблемы появятся я молчаливо его заменю и вы этого уже почти не заметите.
Потребление памяти на серверах оптимизировано, риск обрывов уменьшен.
На данный момент новый бесплатный сервер теряет питание раз в два часа на пять минут.
Если хотите сервера, которые не теряют питание раз в два часа на пять минут, есть платные тарифы.
Чтобы поадресные блокировки РКН как-то ощущались, они должны быть чаще раза в месяц.
Сегодня Ультиму заблокировали (почему-то они обожают блокать именно бесплатный сервер), но как раз пришло время его оплачивать.
И вместо оплаты старого сервера я просто купил новый, не оплачивая старый. За абсолютно ту же цену.
Типа... и что?
Разрешение торрента на нём и так планировалось. Torrent friendly hosting = torrent frien…
Прошло две недели с момента атаки на датацентр ВКонтакте.
Старые фотографии которые я хранил были уничтожены процентов на 80. Просто недоступны.
За суверенный Интернет!
Сегодня тех. проблемы на паре белых серверов.
Старый белый домен ставит рейтлимит на количество подключений и я врезал вас в него. Я несколько часов держал их выключенными чтобы бан спал. Он спал и вернулся за пару минут. Это происходит уже не в первый раз но в прошлые разы получалось восстановиться без последствий, в этот раз нет.
Я использовал новый белый домен, золотой стандарт среди всех белых доменов. По теста…
Я советую использовать open-source нейросети или claude чтобы не чувствовать что к вам относятся как к скотине.
Open-source оптимальнее всего (Deepseek, GLM, Kimi, кого ещё забыл)...
Опять же, я после такого отношения Gemini даже не открываю, кроме того чтобы удостовериться, что он работает. Если от Ютуба я по привычке не могу ещё пока отказаться, то здесь альтернатив слишком много. То что я заставляю что-то работа…
Просили описать что именно было исправлено:
1) Сам формат проверки Gemini немного потерял актуальность и прекратил работать. Был обновлён до актуального, надеюсь повторно этого не случится.
2) Раньше проверка работоспособности Gemini ждала только 30 секунд, а дальше обрывалась без решения. Он может тратить значительно больше времени, и время проверки было повышено до двух минут.
3) На одном из серверов за проверку…
❤27👍3👏1
Showing the 12 most recent of 96 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Польша (нет блокировки на торрент, неограниченные ресурсы, пока что неиспользуемые даже на 10%)64%
Финляндия (меньше пинг, блок на торрент, потребует покупку нового недорогого финского сервера)36%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 96 most recent posts we hold, published 26 July 2026 to 7 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Named by
Channels on the register whose posts name this channel's handle.
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 November 2026 — this
entry's latest reading, not the date you are reading this.
“TOR REBORN” (@Tor_Portable), 8,469 subscribers as measured 10 November 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.