Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝘿𝙖𝙣𝙞𝙡 𝙍𝙤𝙢𝙖𝙣𝙚𝙣𝙠𝙤 | Отзывы

Channel

𝘿𝙖𝙣𝙞𝙡 𝙍𝙤𝙢𝙖𝙣𝙚𝙣𝙠𝙤 | Отзывы

@dandesignerr_feedback

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

1subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002220142975
TypeChannel
Username@dandesignerr_feedback
DescriptionОтзывы
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live17 August 2026
Measurements held2
On Telegramt.me/dandesignerr_feedback

Growth

19 August 2026 — 1 subscribers14 August 2026 — 1 subscribers9 August 202614 August 2026
2 measurements spanning 5 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 13:321no change
9 Aug 2026, 08:301first reading

Engagement

18 posts held, back to 19 March 2025the 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 18 posts for this entry, the most recent from 12 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
24

Lifetime counters from Telegram’s own channel header, read 14 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

12 Jul 2026, 19:42 UTC3 viewsread 14 August 2026
Photo

Отзыв №23 Оформление карточки для маркетплейса | Хинкальница

2 Jun 2026, 04:15 UTC7 viewsread 14 August 2026
Photo

Отзыв №22 Оформление карточки для маркетплейса | Держатель для овощей

16 Jan 2026, 18:07 UTC17 viewsread 14 August 2026
Photo

Отзыв №21 Разработка подарочного сертификата

1 Jan 2026, 14:44 UTC19 viewsread 14 August 2026
Photo

Отзыв №20 Карточки для объявления на Авито

1 Jan 2026, 09:51 UTC19 viewsread 14 August 2026
Photo

Отзыв №19 - Карточки для маркетплейса - чай индийский - Видеообложка для маркетплейса

8 Nov 2025, 15:15 UTC27 viewsread 14 August 2026
Photo

Отзыв №18 Оформление слайдов: Ёмкости для хранения 🔥

22 Oct 2025, 21:26 UTC26 viewsread 14 August 2026
Photo

Отзыв №17 Оформление под сторис 🖥

22 Oct 2025, 07:53 UTC21 viewsread 14 August 2026
Photo

👍 Отзыв №15 Оформление reels для инстаграмма🖥

21 Oct 2025, 07:59 UTC19 viewsread 14 August 2026
Photo

👍 Отзыв №14 Оформление баннеров для Авито 🖥

21 Oct 2025, 07:58 UTC19 viewsread 14 August 2026
Photo

👍 Отзыв №13 Оформление баннеров для Авито 🖥

17 Oct 2025, 12:02 UTC21 viewsread 14 August 2026
Photo

👍 Отзыв №12 Оформление баннеров для Авито 🖥

Showing the 12 most recent of 18 posts we hold for @dandesignerr_feedback. 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 — 662,222 of 1,584,733entries 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 2 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.

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

“𝘿𝙖𝙣𝙞𝙡 𝙍𝙤𝙢𝙖𝙣𝙚𝙣𝙠𝙤 | Отзывы” (@dandesignerr_feedback), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dandesignerr_feedback.

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.