Channel
@ManhattanHub
On this record: Topic · Growth · Engagement · Posts · Cite this entry
711subscribers
-78 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003655837161 |
|---|---|
| Type | Channel |
| Username | @ManhattanHub |
| Created | 28 February 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/ManhattanHub |
Other / unclassifiable — 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 20 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 |
|---|---|---|
| 7 Oct 2026, 06:40 | 711 | -7 |
| 26 Sept 2026, 18:14 | 718 | -16 |
| 10 Sept 2026, 12:42 | 734 | -14 |
| 1 Sept 2026, 11:08 | 748 | -6 |
| 24 Aug 2026, 21:59 | 754 | -17 |
| 16 Aug 2026, 18:03 | 771 | -14 |
| 8 Aug 2026, 12:34 | 785 | -4 |
| 8 Aug 2026, 01:46 | 789 | no change |
| 7 Aug 2026, 19:08 | 789 | first reading |
5 posts held, back to 28 February 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 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 18 June 2026. An engagement rate over an empty window would be a number about nothing.
Быстрый поиск услуг в Mini App @ManhattanHubBot. Мы разработали приложение в Telegram для удобного и быстрого поиска необходимых услуг. Теперь вы можете находить нужное быстро и надежно. Попасть в список контактов: @otdelClub
В последнее время десятки человек пишут модератору каждый день, чтобы заблокировать скамера. В связи с этим советуем воспользоваться услугами гарантов Manhattan Club: ➤ Живой Гарант — @never_MC ➤ Живой Гарант — @MarseillesMC
Реклама в Manhattan Club Автопост на 30 дней: Каждые 120 минут — 190$ Каждые 60 минут — 270$ Закрепленное сообщение на 30 дней — 360$ Реклама в истории: 5 история — 45$ за одну От 10 историй — 37$ за одну Реклама в боте (@ManhattanHubBot): 1 пост — 140$ Баннер Mini App (@ManhattanHubBot): 1 месяц — 190$ Связаться: @otdelClub
Manhattan Club: https://t.me/+AWFX7k3nPp9hM2Y8 Хорошего дня!
Channel created
Showing the 5 most recent of 5 posts we hold for @ManhattanHub. 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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“Manhattan Hub” (@ManhattanHub), 711 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/ManhattanHub.
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.