Telegram RegisterThe public register of Telegram

Channel

Закрытая онлайн конференция - 13 августа

@topcryptoconf1

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

1,776subscribers

-6 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-1003675497017
TypeChannel
Username@topcryptoconf1
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/topcryptoconf1

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 45% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@topcryptoconf1/210 · this entry2 Jul 2026, 17:31 UTC@TopCryptoConf/2122 Jul 2026, 17:31 UTC1.00under a minute
@topcryptoconf1/214 · this entry3 Jul 2026, 16:34 UTC@TopCryptoConf/2133 Jul 2026, 16:34 UTC1.00under a minute
@topcryptoconf1/217 · this entry5 Jul 2026, 15:29 UTC@TopCryptoConf/2165 Jul 2026, 15:32 UTC1.004 minutes
@topcryptoconf1/218 · this entry6 Jul 2026, 15:04 UTC@TopCryptoConf/2176 Jul 2026, 15:04 UTC1.00under a minute
@TopCryptoConf/2187 Jul 2026, 10:01 UTC@topcryptoconf1/219 · this entry7 Jul 2026, 10:02 UTC1.0072 seconds
@TopCryptoConf/2207 Jul 2026, 15:30 UTC@topcryptoconf1/221 · this entry7 Jul 2026, 15:30 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@TopCryptoConf9 (8/8 hand-verifiable sample passed)1.00under a minute@TopCryptoConf (54)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 5 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 14 comparable posts for this entry, running 2 July 2026 to 10 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @topcryptoconf1 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

1,7761,7821,7797 August 2026 — 1,782 subscribers7 August 2026 — 1,782 subscribers8 August 2026 — 1,781 subscribers10 August 2026 — 1,776 subscribers7 August 202610 August 2026
4 measurements spanning 3 days, net -6. 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 1,775–1,783 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 23:381,776-5
8 Aug 2026, 08:041,781-1
7 Aug 2026, 20:491,782no change
7 Aug 2026, 18:531,782first reading

Engagement

20 posts held, back to 2 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 10 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
13s
Average length
13s

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

105 reactions across 19 posts, in 3 distinct kinds. The most used accounts for 64.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥6864.8%
👍2826.7%
98.57%

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

Measured over the 20 most recent posts we hold, published 2 July 2026 to 10 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

10 Jul 2026, 13:37 UTC335 views5 reactionsread 7 August 2026
Video

Друзья, подводим итоги розыгрыша! 🎉 А вот и наши победители: 🏆 100$ в золоте получает владелец счёта 2008288 🏆 Холодный кошелёк получает владелец счета 494212 Поздравляем победителей! 🥳 Если вы владелец одного из этих счетов — напишите нашему представителю (@s_kristisha) Мы расскажем, как получить ваш выигрыш! ✅

🔥5

8 Jul 2026, 12:51 UTC351 views12 reactionsread 7 August 2026

Друзья, привет! 👋 Отправляем вам запись эфира с Иваном Бондаревым ✔️ Максимум пользы без воды ✔️ Доступ закрыт — только для своих 👉 Переходи по ссылке, пока не убрали: https://rutube.ru/video/private/df0b9be4f33054327db573929c85c2ee/?p=ecgkonl8jnov1rRrayyGpw Специальный бонус от Ивана! https://t.me/acryptocryptosensej_bot?start=konfa0626 🔥— если цените то, что мы делаем

🔥12

7 Jul 2026, 16:05 UTC327 views3 reactionsread 7 August 2026
Photo

Присоединиться к конференции Zoom https://us06web.zoom.us/j/87906234854?pwd=3mpWLstBajuj5AEG3l8nhMSpgVXaLA.1

🔥3

7 Jul 2026, 16:00 UTC264 views2 reactionsread 7 August 2026

Начинаем! Подключайтесь 💯

🔥2

7 Jul 2026, 15:57 UTC252 views2 reactionsread 7 August 2026

Друзья, присоединяйтесь к нам на закрытый эфир📈 Время: 7 июл. 2026 07:00 PM Москва Присоединиться к конференции Zoom https://us06web.zoom.us/j/87906234854?pwd=3mpWLstBajuj5AEG3l8nhMSpgVXaLA.1 Ссылка на чат конференции https://us06web.zoom.us/launch/jc/87906234854 Идентификатор конференции: 879 0623 4854 Код доступа: 9Gj3sx

🔥2

7 Jul 2026, 15:30 UTC243 views4 reactionsread 7 August 2026

Друзья, через 30 минут начинаем! Ссылку пришлем сюда за 5 минут до начала эфира. Старт трансляции ровно в 19:00 по МСК У кого нет возможности смотреть эфир - подключайтесь на аудио формат, послушать Ивана Ждем всех на эфире 🤝

🔥4

7 Jul 2026, 10:02 UTC248 views4 reactionsread 7 August 2026

🔥 Уже сегодня в 19:00 состоится закрытый эфир с Иваном Бондаревым! Это отличная возможность получить новые знания, услышать практические рекомендации и задать вопросы одному из спикеров нашей конференции. На эфире обсудим: 📈 Как учиться на чужих сделках и не повторять распространенные ошибки 📈 Как торговать дисциплинированно и без лишней спешки 📈 Почему психология — один из главных факторов успешного трейдинга 🎁

🔥4

6 Jul 2026, 15:04 UTC239 views4 reactionsread 7 August 2026

⏰ Уже завтра — открытый эфир с Иваном Бондаревым! За последние дни мы получили десятки ваших вопросов, и самые актуальные из них разберем в прямом эфире. Поговорим о том: 📈 Как мышление влияет на результаты в трейдинге 📊Как торговать дисциплинированно и без спешки ⚠️ Когда желание заработать становится врагом 💡 Как использовать опыт других для собственного роста Это отличная возможность получить ответы на свои воп

👍4

5 Jul 2026, 15:29 UTC275 views7 reactionsread 7 August 2026

Спасибо за вашу активность! 🚀 Мы видим, насколько вам интересен этот формат, и это вдохновляет делать еще больше полезных встреч. Уже через пару дней состоится закрытый эфир с Иваном Бондаревым. До этого момента у вас есть возможность задать свой вопрос — пишите его в комментариях, и мы постараемся разобрать самые актуальные вопросы💬 🎁 И это еще не все! Среди новых зарегистрированных участников Цифра Маркет разыгр

👍7

Showing the 12 most recent of 20 posts we hold for @topcryptoconf1. 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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“Закрытая онлайн конференция - 13 августа” (@topcryptoconf1), 1,776 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/topcryptoconf1.

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.