16 Aug 2024, 15:52 UTC≈1,630 viewsread 15 August 2026
Беру рест на неопределенный срок.
Channel
Рест. Обратный отсчёт
@Countdown77
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
35subscribers
+0 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001615200083 |
|---|---|
| Type | Channel |
| Username | @Countdown77 |
| Description | Каждое «очарование» влекло за собой неминуемое «разочарование». Навигация — @info_Count |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Countdown77 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 07:15 | 35 | no change |
| 15 Aug 2026, 07:01 | 35 | first reading |
Engagement
17 posts held, back to 14 January 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 pageof 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 17 posts for this entry, the most recent from 16 August 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 274
- Videos
- 2
- Links
- 3
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
28 Jul 2024, 10:30 UTC≈2,220 viewsread 15 August 2026
Когда желания твоего тела совпадут с зовом сердца, а голос разума не воспрепятствует им — только тогда ты обретёшь свободу.
25 Jun 2024, 10:45 UTC≈2,790 viewsread 15 August 2026
На рп брать https://t.me/Countdown77/55934 https://t.me/Countdown77/56944
Signed ✨
25 Jun 2024, 10:44 UTC≈3,190 viewsread 15 August 2026
Люди любят не так, как мы этого заслуживаем и не так, как мы этого хотим. Они любят так, как умеют….
24 May 2024, 14:50 UTC≈4,300 viewsread 15 August 2026
Иногда ты возводишь стены не для того, чтобы не пускать людей, а чтобы посмотреть, кто их сломает.
20 May 2024, 16:35 UTC≈4,590 viewsread 15 August 2026
Ни одно проклятие не может быть более извращённым, чем любовь.
19 May 2024, 06:15 UTC≈3,810 viewsread 15 August 2026
Мы живём с выдуманным образом друг друга и любим несуществующих людей.
20 Mar 2024, 18:59 UTC≈4,610 viewsread 15 August 2026
разреши мне стать твоей луной, и я подарю тебе все свои звезды.
16 Mar 2024, 17:08 UTC≈5,260 viewsread 15 August 2026
Мне не следовало влюбляться. Посмотри, во что это меня превратило.
2 Mar 2024, 13:55 UTC≈6,090 viewsread 15 August 2026
Громче всех кричит тот, кто долго молчал.
21 Feb 2024, 16:10 UTC≈5,240 viewsread 15 August 2026
И я пыталась полюбить снова, но часть меня была твоей.
16 Feb 2024, 17:47 UTC≈3,100 viewsread 15 August 2026
File
File, posted without a caption
Showing the 12 most recent of 17 posts we hold for @Countdown77. 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.
Citation-graph rank
Citation-graph rank — 1,247,526 of 1,548,671entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 5 registered channels — 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Рест. Обратный отсчёт” (@Countdown77), 35 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/Countdown77.
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.