5 Oct 2022, 14:08 UTCviews —
The account of the user that owns this channel has been inactive for the last 11 months. If it remains inactive in the next 9 days, that account will self-destruct and this channel may no longer have an owner.
Channel
•666•
@dushevno_666
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 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 | -1001276816345 |
|---|---|
| Type | Channel |
| Username | @dushevno_666 |
| Created | Between 1 April 2018 and 31 July 2021— 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/dushevno_666 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 03:46 | 1 | no change |
| 14 Aug 2026, 08:47 | 1 | first reading |
Engagement
14 posts held, back to 13 October 2021 — 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 14 posts for this entry, the most recent from 5 October 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 28
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
24 Sept 2022, 11:39 UTCviews —
The account of the user that owns this channel has been inactive for the last 11 months. If it remains inactive in the next 20 days, that account will self-destruct and this channel may no longer have an owner.
14 Sept 2022, 17:02 UTCviews —
The account of the user that owns this channel has been inactive for the last 11 months. If it remains inactive in the next 30 days, that account will self-destruct and this channel may no longer have an owner.
17 Oct 2021, 20:40 UTC60 viewsread 15 August 2026
Прощайте
Signed 🥷
17 Oct 2021, 08:57 UTC69 viewsread 15 August 2026
прощайся с тем, что делает тебя хуже
Signed 🥷
17 Oct 2021, 08:57 UTC68 viewsread 15 August 2026
не смотри на сложности, находи возможности))
Signed 🥷
17 Oct 2021, 08:50 UTC69 viewsread 15 August 2026
мне понадобилось уйму времени, чтобы понять одно. Никогда не поздно начать все сначала, мне пришлось уйти на самое дно. Чтоб потом ты мной восхищалась.
Signed 🥷
14 Oct 2021, 22:18 UTC98 viewsread 15 August 2026
Photo
Photo, posted without a caption
Signed 🥷
14 Oct 2021, 22:15 UTC56 viewsread 15 August 2026
даже осенью можно быть чей-то весной
Signed 🥷
14 Oct 2021, 22:15 UTC53 viewsread 15 August 2026
в небе сияют звезды, но не ярче твоих глаз.
Signed 🥷
14 Oct 2021, 22:15 UTC53 viewsread 15 August 2026
на счет носа стоит комплексовать тем, кто сует его не в свои дела
Signed 🥷
13 Oct 2021, 22:52 UTC97 viewsread 15 August 2026
все что было тебе дорого, рано или поздно всё равно уйдёт))
Signed 🥷
Showing the 12 most recent of 14 posts we hold for @dushevno_666. 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,453,076 of 1,481,306entries 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 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“•666•” (@dushevno_666), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/dushevno_666.
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.