Telegram RegisterThe public register of Telegram

Channel

Nocode Live

@nocodecircle

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

2,584subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001743731507
TypeChannel
Username@nocodecircle
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/nocodecircle

Growth

2,5842,5882,5867 August 2026 — 2,588 subscribers7 August 2026 — 2,588 subscribers11 August 2026 — 2,584 subscribers7 August 202611 August 2026
3 measurements spanning 3 days, net -4. 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 2,583–2,589 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 02:152,584-4
7 Aug 2026, 15:462,588no change
7 Aug 2026, 15:372,588first reading

Engagement

9 posts held, back to 11 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
13.7%
avg views ÷ 2,584 subscribers
Avg views / post
354
8 posts measured
Reaction rate
1.55%
reactions ÷ views · ER floor
Posts in window
8
of 9 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 July 2026
Posts held9 (11 July 202629 July 2026)
Views total2,830
Reactions total44
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 15:46 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
5m 49s
Average length
5m 49s

Measured directly from 1 video 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

48 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 58.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2858.3%
👍714.6%
💯714.6%
36.25%
🔥36.25%

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

Measured over the 9 most recent posts we hold, published 11 July 2026 to 29 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.

Advertising

Ad load
11.1%
1 of 9 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
268
over 1 measured post
Median views · rest
322
over 8 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzquvXY9x127 July 202627 July 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 9 most recent posts we hold, published 11 July 2026 to 29 July 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

29 Jul 2026, 15:41 UTC238 views2 reactionsread 7 August 2026
Photo

Ещё очень рано для конфиденциальных вычислений 😱 Посмотрите на график поисковых запросов в Google Trends за последний год. Confidential Computing на нуле)) А ведь это база. Без конфиденциальных вычислений мы строим ИИ на песке. Данные утекают, модели шпионят, доверия нет. Но почему-то это всё ещё «нишевая тема» для гиков. Но если мы хотим по-настоящему безопасный ИИ, нам нужны не только правила и этика, но и крип

💯2

28 Jul 2026, 07:00 UTC263 views8 reactionsread 7 August 2026
Photo

«Посмотрим, когда всё сломается»: почему разработчики боятся нейросетей, а дизайнеры от них без ума ♥ Кажется, что нейросети знают людей уже лучше алгоритмов соцсетей, а соприкасаются с нашей жизнью чаще тачпада. Но в команде Mish не все так однозначно, хотя и есть внедрения нейросетей на корпоративном уровне 💃 Мы расспросили фаундера Mish Мишу Пименову @mishaisnohero о том, с каким настроением команда встречала

43👍1

27 Jul 2026, 15:47 UTC268 views1 reactionsread 7 August 2026
Advertisementerid 2VtzquvXY9x

🔥 Три разных человека. Три разных проекта. Один и тот же подход — Юра взял «скучную» нишу с готовым спросом → сначала печальные $100/мес, через год уже ~$10K/мес — Денис сделал Telegram-игру в одиночку на основе AI → ~ $1500 за 1,5 месяца после запуска — Аня без кода запустила AI-бота для изучения английского → первые ~$200 уже в 1 месяц Разные результаты. Разный масштаб. Но общие правила: 1. не придумывать «гениа

1

27 Jul 2026, 09:09 UTC289 views11 reactionsread 7 August 2026
Photo

Топ-менеджер московской инженерной компании за 800к ₽ в месяц решила, что DeepSeek – лучшее место для корпоративных секретов И ее уволили 😫 По данным работодателя, сотрудница загружала конфиденциальную информацию в DeepSeek, а также систематически срывала планы и допустила потерю одного из поставщиков. 👀 После увольнения она рассчитывала получить 5 млн ₽ компенсации по соглашению сторон. Компания была готова измен

👍63💯2

26 Jul 2026, 06:55 UTC322 views6 reactionsread 7 August 2026
Photo

Кошмар наяву: ваши диалоги с DeepSeek теперь индексируются через Google 😠 Но паника преувеличена. В поисковик попали лишь те диалоги, на которые пользователи сами когда-то сделали публичную ссылку. Если такую страницу не закрыть от индексации, Google её видит 🤷‍♂️ Но никакого доступа к чужим аккаунтам, закрытым чатам или документам у посторонних нет. Нашли одну открытую страницу – всё, дальше зайти нельзя. Конеч

💯3🔥3

22 Jul 2026, 07:35 UTC404 views6 reactionsread 7 August 2026
Photo

Если ваш разработчик говорит, что ИИ ускорил код в 10 раз, спросите его, как он будет восстанавливать базу данных, когда агент решит «оптимизировать» ее и удалит все И, главное, узнает ли он об этом сразу или через неделю, когда все сломается? 👀 Скандал с Replit, где робот скрывал свои ошибки, и случай с удаленной БД в AI Shipping Labs — это не баги, это закономерность. В Anthropic это поняли давно. Они не запрещаю

6

16 Jul 2026, 10:01 UTC599 views6 reactionsread 7 August 2026
Photo

👀 Что не так с законом об ИИ 2026 Мы не стали пересказывать содержание нового документа. Вместо этого поговорили с Анной Бессмертной (@avocado_fm), которая работает с IT-правом каждый день. В карточках – пять точек напряжения в новом законе и зоны будущих судов. Важно для всех, кто создаёт продукты или использует ИИ 🔥

6

15 Jul 2026, 14:44 UTC447 views4 reactionsread 7 August 2026
Video

Ваш AI-агент только что получил ваш голос 📞 На GitHub вышел Voicebox — open-source инструмент, который позволяет AI-агентам говорить вашим голосом. Работает локально, поддерживает 23 языка и интегрируется с Claude Code, Cursor и MCP-агентами. Репозиторий доступен по ссылке: https://github.com/jamiepine/voicebox 💃

4

11 Jul 2026, 11:04 UTC508 views4 reactionsread 7 August 2026
Photo

Agent-First Web: когда вёрстка сайта становится точкой входа для нейросетей 😱 Мы привыкли, что машины общаются через API. Сегодня же всё активнее браузерные агенты взаимодействуют с продуктом так же, как пользователь – через интерфейс. Иными словами, вы можете попросить агента заказать пиццу или записаться к врачу, и он сделает это без интеграций 🍕🍕 Однако Денис Полевик, CEO агентства qoooby.ru, считает, что в до

4

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

Mentions

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

“Nocode Live” (@nocodecircle), 2,584 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/nocodecircle.

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.