Telegram RegisterThe public register of Telegram
Telegram profile photo for [переезд] ĆHAŞE#HUB . . ERÂ

Channel

[переезд] ĆHAŞE#HUB . . ERÂ

@chasovskiyi

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

228subscribers

-6 since we began measuring on 14 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001953136248
TypeChannel
Username@chasovskiyi
Created11 July 2023measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live12 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 12 September 2026
On Telegramt.me/chasovskiyi

Growth

22823423114 August 2026 — 234 subscribers14 August 2026 — 234 subscribers15 August 2026 — 233 subscribers22 August 2026 — 231 subscribers5 September 2026 — 228 subscribers14 August 20265 September 2026
5 measurements spanning 22 days, net -6. 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 227–235 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 02:41228-3
22 Aug 2026, 10:37231-2
15 Aug 2026, 02:47233-1
14 Aug 2026, 07:45234no change
14 Aug 2026, 07:33234first reading

Engagement

16 posts held, back to 11 July 2023the 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 16 posts for this entry, the most recent from 9 November 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

9 Nov 2024, 16:38 UTC841 viewsread 14 August 2026

союзники @tonynyw69, ЗА ПЕРЕЗАКЛЮЧЕНИЕМ МНЕ В ЛС!!!!!!!!!!

Signed ironman psy

9 Nov 2024, 15:15 UTC870 viewsread 14 August 2026

Так, чейзовские возвращаются ПЕРЕЕЗД : https://t.me/chasovskiie https://t.me/chasovskiie https://t.me/chasovskiie те, кто хочет сразу же союз - ищем в навигации правила союза и пишем одному из админов

Signed hypøcrite.chv

28 Oct 2024, 09:59 UTC≈1,170 viewsread 14 August 2026

дайте нам ньюшек, будем вас любить, кормить да

Signed ironman

24 Oct 2024, 11:14 UTC≈1,330 viewsread 14 August 2026

сделайте рп пожалуйста

Signed ironman

24 Oct 2024, 11:11 UTC≈1,960 viewsread 14 August 2026

итак, мои котята произошли некоторые изменения, и я спешу заявить, что чейзовские закрываются ладно, никуда мы не закрываемся на самом деле, мы закрываем этот канал, и это означает что чейзовские переезжают планы поменялись, и мы вернёмся в декабре, 2024 года, и начнём все с абсолютного чистого листа все союзы разрываются, но попрошу вас оставить юзы ваших каналов в комментариях, если хотите продолжать сотрудничат

Signed ironman

24 Oct 2024, 10:27 UTC≈1,020 viewsread 14 August 2026

‼️ союзники ( @hharrins ), которые хотят сохранить союз, пожалуйста отпишитесь (@tonynyw69) для нового союза ‼️

Signed ironman

24 Oct 2024, 09:05 UTC≈1,830 viewsread 14 August 2026

короче , я не буду мусолить и писать тексты Я ухожу с должности владельца чейзовских. Все мои союзы @hharrins разрываются. Удачи вам

Signed рест

1 Sept 2024, 11:55 UTC≈6,330 viewsread 14 August 2026
Photo

🩸SET$IN ĆHÂT . . CHASE\\HUB . . 🌟 для вступление в наш чат, вы обязаны : 🌟поставить инициал 🌟 прочитать правила 🌟подписаться на канал 🌟подать заявку в

1 Sept 2024, 11:52 UTC≈3,900 viewsread 14 August 2026
Photo

🎵NAVIGATING . . . CHASE$HUB🩸 чейзовские - место и люди, которые окутают тебя чувством безмятежности и уюта. перешагни порог неизвестности, став частью нашей семьи. ➿➿➿➿➿➿➿➿➿➿ CHAT 🌟 PÆTÈNȚ UNIÓN AŅOÑ $ AÐMÍNS 🌟INĨȚIAL

Showing the 12 most recent of 16 posts we hold for @chasovskiyi. 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

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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“[переезд] ĆHAŞE#HUB . . ER” (@chasovskiyi), 228 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/chasovskiyi.

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.