Telegram RegisterThe public register of Telegram
Telegram profile photo for 🩶𝙜𝙧𝙖𝙬 𝙗𝙧𝙤𝙬𝙣 𝙠𝙤𝙣𝙤𝙗𝙡𝙤𝙜🤎 | 𝒆𝒒 𝒌𝒂𝒅𝒓𝒊𝒍🪷

Channel

🩶𝙜𝙧𝙖𝙬 𝙗𝙧𝙤𝙬𝙣 𝙠𝙤𝙣𝙤𝙗𝙡𝙤𝙜🤎 | 𝒆𝒒 𝒌𝒂𝒅𝒓𝒊𝒍🪷

@kadriltopi

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

388subscribers

+33 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-1002121289312
TypeChannel
Username@kadriltopi
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live16 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/kadriltopi

Topic

Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

35540538014 August 2026 — 355 subscribers14 August 2026 — 355 subscribers15 August 2026 — 358 subscribers23 August 2026 — 391 subscribers30 August 2026 — 405 subscribers9 September 2026 — 392 subscribers16 September 2026 — 388 subscribers38814 August 202616 September 2026
7 measurements spanning 33 days, net +33. 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 348–413 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 09:18388-4
9 Sept 2026, 15:41392-13
30 Aug 2026, 21:45405+14
23 Aug 2026, 10:17391+33
15 Aug 2026, 17:58358+3
14 Aug 2026, 19:31355no change
14 Aug 2026, 19:23355first reading

Engagement

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

What this channel posts

Video runtime
1m 13s
Average length
18s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

42 reactions across 5 posts, in 8 distinct kinds. The most used accounts for 31.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53865176392521849041331.0%
custom 5445163665332410316819.0%
511.9%
🔥511.9%
💘49.52%
🤯37.14%
custom 530563534770985547924.76%
🆒24.76%

Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 5 of the 7 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 42 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 11 August 2026 to 14 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

14 Aug 2026, 18:13 UTC17 viewsread 14 August 2026

фото батл с моим спонсорством,участвуйте)

14 Aug 2026, 18:13 UTC7 viewsread 14 August 2026
Forwarded from @Jesti_konnogo_miraPhoto

❤️‍🔥❤️‍🔥❤️‍🔥❤️‍🔥 ❤️‍🔥❤️‍🩹❤️‍🔥❤️‍🔥 Призы: ❤️‍🔥 Место - Лизунец ❤️‍🔥 Место - Лизунец ❤️‍🔥 Место - Лизунец (Вкус можно будет выбрать в рамках бюджета, или поменять на 50% стоимости, обсуждается с победителем)❤️‍🔥 Условия: ❤️‍🔥Подписка на: Спонсор 1 (527) Спонсор 2 (335) Спонсор 3 (43) Спонсор 4 (77) Канал организатор (1547) ❤️‍🔥Рассыл 7+ чатов/тгк от 50+ ❤️‍🔥Иметь пункт выдачи Озон Туда придет посылка ❤️‍🔥❤️‍🔥❤️‍🔥

14 Aug 2026, 12:03 UTC34 views10 reactionsread 14 August 2026
Photo

🆕🆕 ~ а сегодня Репа гулял в леваде и я там немного побыла с ним🤩 затем гоняли Саванну на корде🥳 после я ее почистила #Саванна #Репаратор

5💘2🔥2custom 53865176392521849041

14 Aug 2026, 11:59 UTC28 views6 reactionsread 14 August 2026
Photo

🆕🆕 ~ 13.08 ездила на Лахти попрыгали до 75 где то она отлично все прыгала прям🌟 по началу мне приходилось её прям очень сильно сдерживать,но потом она под успокоилась и уже было лучше🌹 а Репушку помыла и паслись🌟 #Лахти #Репаратор

💘2🆒2custom 53865176392521849042

14 Aug 2026, 11:57 UTC32 views8 reactionsread 14 August 2026
Photo

🆕🆕 ~ 12.08 с Репой были на лайте прям😸 я выставила маршрут из кавалетти проезжали на шагу,рыси и галопе ещё заметили что он как то очень немного,но прихрамывал поэтому я не работаю его,на след неделе посмотрим🙏🏻 #Репаратор

custom 53865176392521849044custom 53056353477098554792custom 54451636653324103162

11 Aug 2026, 10:47 UTC63 views9 reactionsread 14 August 2026
Photo

🆕🆕 ~ а уже ближе к 15 часам я пошла попасти Репу решила пойти до левады,и оказывается президент ещё проедет мимо нас,уже до Скифа с Репушкой встречали второй раз🤎 а после попаслись немного и пошли гулять🤩 #Репаратор

🔥3custom 53865176392521849043custom 54451636653324103163

11 Aug 2026, 10:38 UTC55 views9 reactionsread 14 August 2026
Photo

🆕🆕 ~ дальше я пошла быстро пересаживаться на Репку оперативно его собрала немного попрыгали побегали и мы вместе с девочками встречали В.В. Путина были на Ночке 2,Чаре,ну и я на Репе🤩 в общей сумме мы проездили 2.5ч👌 + поснимали на сифончик🌟 после я отвела Репу в леваду пастись #Репаратор

🤯3custom 53865176392521849043custom 54451636653324103163

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“🩶𝙜𝙧𝙖𝙬 𝙗𝙧𝙤𝙬𝙣 𝙠𝙤𝙣𝙤𝙗𝙡𝙤𝙜🤎 | 𝒆𝒒 𝒌𝒂𝒅𝒓𝒊𝒍🪷” (@kadriltopi), 388 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/kadriltopi.

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.