23 Apr 2024, 12:33 UTC74 viewsread 14 August 2026
Photo
@Demi_lav спасибо за быструю сделку, буду обращаться ещё. Рекомендую 🎈☺️
Channel
отзывы || Деми
@otzivdm
On this record: Growth · Engagement · Posts · Citations · Cite this entry
7subscribers
+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 | -1001893097994 |
|---|---|
| Type | Channel |
| Username | @otzivdm |
| Created | Between 1 October 2022 and 27 July 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/otzivdm |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 03:38 | 7 | no change |
| 14 Aug 2026, 03:02 | 7 | first reading |
Engagement
20 posts held, back to 27 July 2023 — 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 20 posts for this entry, the most recent from 23 April 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
3 Apr 2024, 06:30 UTC102 viewsread 14 August 2026
Photo
Провели сделку на 15к через @Demi_lav. Все быстро и четко🤝
15 Mar 2024, 17:06 UTC109 viewsread 14 August 2026
Photo
Спасибо огромное Деми за сделку. Быстро и качественно всё прошло. Человек знает своё дело, поэтому смело можно обращаться к @Demi_lav
26 Feb 2024, 17:06 UTC95 viewsread 14 August 2026
Photo
Купил канал у @Demi_lav, всё ахн!!
30 Jan 2024, 14:34 UTC138 viewsread 14 August 2026
Photo
@Demi_lav канал стоял несколько месяцев и никто его брал, везде был скам. но в этот раз я не пожалел, правда, и избавился от этой ноши, ахха. спасибо деми за содействие и быструю продажу.
30 Jan 2024, 14:33 UTC131 viewsread 14 August 2026
Photo
@Demi_lav спасибо за сделку, все быстро и качественно 🙂
27 Jan 2024, 15:40 UTC110 viewsread 14 August 2026
Photo
@Demi_lav спасибо за проведенную сделку, все отлично, буду общаться ещё
23 Dec 2023, 15:18 UTC195 viewsread 14 August 2026
Photo
Продал канал через деми) Все прошло быстро приятно, замечательно было страшно. Спасибо огромное 😉 @Demi_lav
16 Dec 2023, 19:50 UTC199 viewsread 14 August 2026
Photo
Проводили сделку через деми @Demi_lav Все быстро, четко, главное бесплатно. Вернусь еще
7 Nov 2023, 14:33 UTC245 viewsread 14 August 2026
Photo
Взяла место в сетке у @Demi_lav. Беру уже не первый раз. Все радует как и всегда, особенно за такую цену) люди пошли моментально, даже активят в чате. Рекомендую❤️
15 Oct 2023, 15:51 UTC357 viewsread 14 August 2026
Photo
@Demi_lav Прекрасный гарант без наеба, в сети часто и сразу отвечает, делает все быстро и без лишних разговоров, а самое главное за работу берет лишь отзывы, без денег. Всем советую
15 Oct 2023, 15:48 UTC298 viewsread 14 August 2026
@Demi_lav спасибо за хорошие услуги гаранта 💋👍
Showing the 12 most recent of 20 posts we hold for @otzivdm. 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,000,680 of 1,480,688entries 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
“отзывы || Деми” (@otzivdm), 7 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/otzivdm.
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.