Telegram RegisterThe public register of Telegram
Telegram profile photo for The Kulikova Code

Channel

The Kulikova Code

@kulikova_code

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

48subscribers

+22 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-1003742966033
TypeChannel
Username@kulikova_code
CreatedBetween 1 February 2026 and 8 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/kulikova_code

Growth

264937.57 August 2026 — 26 subscribers11 August 2026 — 26 subscribers23 August 2026 — 44 subscribers29 August 2026 — 48 subscribers8 September 2026 — 49 subscribers17 September 2026 — 48 subscribers487 August 202617 September 2026
6 measurements spanning 40 days, net +22. 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 23–52 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 02:2248-1
8 Sept 2026, 16:1949+1
29 Aug 2026, 19:0948+4
23 Aug 2026, 00:5244+18
11 Aug 2026, 09:0126no change
7 Aug 2026, 21:1626first reading

Engagement

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

What this channel posts

Video runtime
1m 49s
Average length
27s

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

54 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 48.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2648.1%
🔥1425.9%
🥰814.8%
❤‍🔥611.1%

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

Measured over the 5 most recent posts we hold, published 8 June 2026 to 28 July 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

28 Jul 2026, 16:53 UTC60 views21 reactionsread 11 August 2026
Photo

Ну и самое сладкое: фото клуба, каким я его когда-то взяла (простите за качество, но это моя память) 💔 Даже не верится… Помню, был момент, когда у меня в начале 2019 года приехала фура новых классных Американских беговых дорожек. Фура пришла раньше времени - на 5 дней, спец сборщики и грузчики были на выезд в Самару и должны были приехать только через неделю. Я очень хотела запустить новую большую кардио-зону как мо

🔥107🥰4

28 Jul 2026, 16:36 UTC531 views13 reactionsread 11 August 2026
Video

Иногда одна награда может напомнить, какой огромный путь уже пройден. Сегодня FitnessBoom Ново-Садовая получил награду «Лучший фитнес-клуб Промышленного района Самары» по версии 2ГИС. И для меня это гораздо больше, чем награда. В 2018 году мы приняли этот клуб совсем другим. Если честно, многие не верили, что из него можно сделать современный фитнес-клуб. Старое оборудование, отсутствие ремонта, изношенные залы, ус

6❤‍🔥4🥰2🔥1

14 Jun 2026, 06:39 UTC135 views11 reactionsread 11 August 2026
Photo

Мой подход к клиентам на очень простом примере Немного расскажу, как я выбираю товар/оборудование/услугу для наших клиентов. На примере простой вроде бы вещи, но важной для фитнес-клуба, - фенов для волос. Во всех моих фитнесах стоят фены, как у меня дома, это профессиональная и очень хорошая линейка. Я с трепетом отношусь к здоровью своих волос (моя длина и густота), и с таким же трепетом отношусь к здоровью волос

7🔥2🥰2

8 Jun 2026, 03:55 UTC121 views9 reactionsread 11 August 2026
Photo

Встреча с Главой г.о. Самара Пригласили на встречу с Носковым Иваном Николаевичем, с удовольствием приехала и выступила. Еще раз от Самарского Спортивного Альянса: Огромное спасибо за диалог с нами и за такой интерес к нашим трудам и стараниям. Поверьте, мне есть с чем сравнить (в разных городах власти коммуницируют по-разному со спорт сообществами). В Самаре очень классный Департамент Спорта и все причастные к нем

6❤‍🔥2🔥1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“The Kulikova Code” (@kulikova_code), 48 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/kulikova_code.

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.