Демо-ссылка тарифа Standard: http://demo.tsarea.tv:8880 https://demo.tsarea.tv:8443 - Размер файла: до 50ГБ - Лимиты: трафик 5ГБ/час и 50ГБ/день. Демо-ссылка тарифа PLUS: http://demoplus.tsarea.tv:8880 https://demoplus.tsarea.tv:8443 - Размер файла: ∞ - Лимиты: трафик 10ГБ/час и 50ГБ/день. А так же 7 дней в месяц использования ссылок суммарно. Все перечисленные ограничения - только для демо. С TorrStream демо-ссы…

Channel
TSArea - torrserver demo
@tsareademo
On this record: Topic · Growth · Engagement · Posts · Cite this entry
4,012subscribers
+309 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001658672954 |
|---|---|
| Type | Channel |
| Username | @tsareademo |
| Created | 26 January 2022 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/tsareademo |
Topic
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 16:56 | 4,012 | +10 |
| 4 Nov 2026, 03:31 | 4,002 | +13 |
| 1 Nov 2026, 11:26 | 3,989 | +12 |
| 29 Oct 2026, 03:30 | 3,977 | +5 |
| 26 Oct 2026, 08:19 | 3,972 | +12 |
| 23 Oct 2026, 00:28 | 3,960 | -22 |
| 20 Oct 2026, 09:46 | 3,982 | +7 |
| 17 Oct 2026, 16:46 | 3,975 | +12 |
| 14 Oct 2026, 16:05 | 3,963 | +26 |
| 10 Oct 2026, 22:01 | 3,937 | +22 |
| 4 Oct 2026, 23:00 | 3,915 | +38 |
| 25 Sept 2026, 08:37 | 3,877 | +30 |
| 15 Sept 2026, 07:00 | 3,847 | +13 |
| 11 Sept 2026, 15:41 | 3,834 | +8 |
| 7 Sept 2026, 07:36 | 3,826 | +2 |
| 2 Sept 2026, 14:23 | 3,824 | +1 |
| 30 Aug 2026, 06:05 | 3,823 | +19 |
| 27 Aug 2026, 04:29 | 3,804 | +18 |
| 23 Aug 2026, 22:47 | 3,786 | +19 |
| 20 Aug 2026, 17:12 | 3,767 | first reading |
Engagement
2 posts held, back to 26 January 2022 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 3 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 2 posts for this entry, the most recent from 4 March 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
Channel created
Showing the 2 most recent of 2 posts we hold for @tsareademo. 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“TSArea - torrserver demo” (@tsareademo), 4,012 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/tsareademo.
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.