Кабинет/Билинг Заработал решили проблему с сессиями

Channel
ASTRACAT UO
@AstracatUO
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,189subscribers
+54 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 | -1002948954585 |
|---|---|
| Type | Channel |
| Username | @AstracatUO |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/AstracatUO |
Topic
Gaming — 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 13 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 19:17 | 4,189 | +13 |
| 13 Sept 2026, 20:20 | 4,176 | +40 |
| 10 Sept 2026, 06:57 | 4,136 | -22 |
| 5 Sept 2026, 02:37 | 4,158 | -5 |
| 1 Sept 2026, 09:35 | 4,163 | +16 |
| 29 Aug 2026, 10:38 | 4,147 | +29 |
| 26 Aug 2026, 13:22 | 4,118 | -2 |
| 23 Aug 2026, 17:04 | 4,120 | +1 |
| 20 Aug 2026, 11:52 | 4,119 | +1 |
| 17 Aug 2026, 12:35 | 4,118 | -15 |
| 14 Aug 2026, 06:57 | 4,133 | +9 |
| 11 Aug 2026, 06:47 | 4,124 | -9 |
| 8 Aug 2026, 16:02 | 4,133 | -2 |
| 7 Aug 2026, 17:47 | 4,135 | no change |
| 7 Aug 2026, 17:33 | 4,135 | first reading |
Engagement
22 posts held, back to 22 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 4 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 22 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
130 reactions across 17 posts, in 9 distinct kinds. The most used accounts for 33.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 44 | 33.8% | |
| 🔥 | 37 | 28.5% | |
| 👍 | 24 | 18.5% | |
| 👀 | 11 | 8.46% | |
| 😢 | 5 | 3.85% | |
| 👏 | 3 | 2.31% | |
| 🤯 | 3 | 2.31% | |
| 🥰 | 2 | 1.54% | |
| 😱 | 1 | 0.769% |
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 17 of the 22 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 130 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 22 July 2026 to 8 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
Кабинет/Билинг починили Исправили проблему с сессиями
пофиксили бс vlees будет работать :)
Сегодня в 18:00 по МСК в тестовом режиме будет разрешено скачивание торрентов 📥⏰
БС и qWDTT заработают в течении 24 часов Всем будет выдана компенсация
👍5
Решено Вcе в штатном режиме :)
❤7
Технические работы по CDN сети Затронули: Билинг,Обновления подписки,DNS-OverHTTPS ETA-2.5 часов
❤5
🧐 В ASTRACAT BillingManager появились новые функции! Мы продолжаем делать управление подписками проще и удобнее. Теперь в личном кабинете доступны две новые возможности. 😏 Возврат подписки Оформить возврат теперь можно самостоятельно через биллинг: — в течение 3 дней после покупки; — для покупок стоимостью от 100 ₽; — со статусом возврата прямо в личном кабинете. Если возврат недоступен, биллинг сразу покажет причину…
❤5
🚀 Сегодня в личный кабинет ASTRACAT будет добавлено небольшое, но очень полезное обновление! Теперь вы сможете: 🏷 Оформлять несколько подписок на одном аккаунте. 🏷 Управлять каждой подпиской отдельно. 🏷 Быстро переключаться между ними без лишних действий. Но это только начало. 💬 Поддержка ASTRACAT переезжает прямо в биллинг! Теперь создавать обращения и отслеживать их статус можно будет прямо в личном кабинете. …
🔥7👀1👍1
✌️ Уважаемые пользователи, миграция с OlcRTC на qwdtt успешно завершена! Чтобы получить свою ссылку wdtt://: Зайдите в биллинг: cabinet.astracat.ru Откройте вкладку qwdtt Скопируйте персональную ссылку и добавьте её в клиент В некоторых случаях потребуется ручная миграция. Всё просто: нажмите кнопку «Мигрировать на qwdtt», подождите несколько секунд — и ваш ключ готов! БЕЗ САППОРТА. БЕЗ ГЕМОРОЯ. БЕЗ СТРЕССА. 🙁 😇 Если…
👍3🤯2
👷♂️ Важное объявление для пользователей ASTRACAT К сожалению, нам не удалось реализовать стабильную работу OlcRTC на необходимом уровне. Поэтому мы приняли решение отказаться от него и вернуть qwdtt. Мы постараемся провести миграцию максимально быстро и комфортно. От вас потребуется только вставить новый ключ qwdtt в клиент — после этого подключение снова будет работать. Также всем пользователям будет начислена комп…
❤5😢3
🚀 Встречайте ASTRACAT Billing Manager! Это не просто очередное обновление — мы полностью переосмыслили концепцию нашего биллинга и создали собственную полноценную систему управления подписками. Главный приоритет — стабильность и безопасные миграции. Предыдущий переход с Vk Tunnel оказался крайне неудачным и создал множество проблем. Мы сделали выводы: такие ситуации больше не должны затрагивать клиентов и вынуждать…
👍10❤1👏1🔥1
Showing the 12 most recent of 22 posts we hold for @AstracatUO. 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 1 registered channel — 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“ASTRACAT UO” (@AstracatUO), 4,189 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/AstracatUO.
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.