Channel
@rekomendacii_3_14
On this record: Topic · Growth · Engagement · Posts · Cite this entry
435subscribers
-11 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002024618094 |
|---|---|
| Type | Channel |
| Username | @rekomendacii_3_14 |
| Created | 16 February 2024 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/rekomendacii_3_14 |
Hacking & security — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 06:38 | 435 | -3 |
| 6 Sept 2026, 05:42 | 438 | -1 |
| 29 Aug 2026, 00:14 | 439 | -2 |
| 22 Aug 2026, 11:58 | 441 | -2 |
| 14 Aug 2026, 15:58 | 443 | -2 |
| 8 Aug 2026, 05:04 | 445 | no change |
| 7 Aug 2026, 23:30 | 445 | -1 |
| 7 Aug 2026, 15:20 | 446 | first reading |
5 posts held, back to 16 February 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 5 posts for this entry, the most recent from 30 November 2025. An engagement rate over an empty window would be a number about nothing.
#Прокси - @resproxyca_bot 1. Статический айпи под гугл акки, с 0 риск скора. На 30/60/90 дней с возможностью продления. Безлим трафик 2. Резики под другие источники с ротацией, в зависимости от гео - можно фиксировать айпишник до максимум недели. Оплата за использованные гб. Вечный промокод на 15% к каждому заказу = "3.14"
#клоака - tds.ad Многофункциональный комбайн включающий в себя КЛОАКУ+ ТДС+ ХОСТИНГ из коробки.
#Аккаунты google @sergingose спендовые гугл адс аккаунты. аккаунты с верифом. разбаны. аккаунты под заказ. @chef_ads Гугладс аккаунты со спендом разных гео
Администрация НЕ НЕСЕТ(!!!) ответственности за список рекомендаций! ВСЕ СЕРВИСЫ БЕЗ РЕФКИ! Нет никакой коммерческой составляющей от рекомендаций. Не хотите - не используйте. Сюда НЕ попадут те кого НЕ пропустит администрация. Тот кто находится в рекомендациях - находится здесь после проведенных тестов.
Channel created
Showing the 5 most recent of 5 posts we hold for @rekomendacii_3_14. 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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Список рекомендаций 3.14” (@rekomendacii_3_14), 435 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/rekomendacii_3_14.
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.