Telegram RegisterThe public register of Telegram
Telegram profile photo for ОТЗЫВЫ

Channel

ОТЗЫВЫ

@JKotziv

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

195subscribers

-8 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002088430690
TypeChannel
Username@JKotziv
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/JKotziv

Growth

195204199.57 August 2026 — 203 subscribers8 August 2026 — 203 subscribers8 August 2026 — 204 subscribers16 August 2026 — 203 subscribers24 August 2026 — 200 subscribers30 August 2026 — 197 subscribers8 September 2026 — 195 subscribers7 August 20268 September 2026
7 measurements spanning 32 days, net -8. 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 194–205 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 15:57195-2
30 Aug 2026, 16:58197-3
24 Aug 2026, 17:08200-3
16 Aug 2026, 09:05203-1
8 Aug 2026, 14:23204+1
8 Aug 2026, 11:19203no change
7 Aug 2026, 18:42203first reading

Engagement

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

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💅1100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 1 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 13 July 2026 to 4 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Aug 2026, 09:53 UTC56 viewsread 8 August 2026

Спасибо, огромное. Кроссвоки пришли. Качество наилучшее, просто обожаю у вас заказывать, размер прям идеально подошел

3 Aug 2026, 13:34 UTC73 viewsread 8 August 2026

Секс, удобно, размер тоже тот что нужен, в общем спасибо большое

3 Aug 2026, 13:34 UTC73 viewsread 8 August 2026

Спасибо большое, нашли модель, заказали, отправили. Я доволен

30 Jul 2026, 09:50 UTC110 viewsread 8 August 2026

Ровно два года назад я получил эту пару, и за два года полной эксплуатации с ними НИЧЕГО не случилось. На них не стерлась подошва, ни оторвались материалы, язычок не потерялся, буквы на месте. Поэтому выбор пал на точно такие-же, только в другом цвете)

30 Jul 2026, 09:48 UTC96 viewsread 8 August 2026
Photo

Здравствуйте, забрал кроссовки, очень сильно их ждал. Что на фотографии, что в жизни они смотрятся невероятно круто, качество как всегда на высшем уровне🔥

29 Jul 2026, 17:50 UTC96 viewsread 8 August 2026
Photo

как всегда замечательно шеф, ты лучший

18 Jul 2026, 11:40 UTC163 viewsread 8 August 2026

Крутые NB 1906r. Сделаны качественно, слабое место этой пары - завязки, которые держат шнурки, здесь они сделаны более плотно, как мне показалось. Все круто)

16 Jul 2026, 14:22 UTC200 viewsread 8 August 2026
Photo

Сегодня забрал, очень нравятся, единственное немного маловаты, но я думаю разносятся

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

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

“ОТЗЫВЫ” (@JKotziv), 195 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/JKotziv.

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.