Telegram RegisterThe public register of Telegram

Channel

Sikorsky Trade | Трейдинг, инвестиции в криптовалюты, акции и IPO

@iamkchelovek

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

20,342subscribers

+2,265 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001268140977
TypeChannel
Username@iamkchelovek
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/iamkchelovek

Topic

Crypto & trading — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 74% 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
@bogdanoffinvest/122025 Aug 2026, 16:00 UTC@iamkchelovek/5529 · this entry5 Aug 2026, 16:00 UTC1.00under a minute
@bogdanoffinvest/122086 Aug 2026, 09:51 UTC@iamkchelovek/5530 · this entry6 Aug 2026, 09:51 UTC1.00under a minute
@bogdanoffinvest/122116 Aug 2026, 10:32 UTC@iamkchelovek/5531 · this entry6 Aug 2026, 10:32 UTC1.00under a minute
@bogdanoffinvest/122187 Aug 2026, 04:02 UTC@iamkchelovek/5532 · this entry7 Aug 2026, 04:02 UTC1.00under a minute
@bogdanoffinvest/122207 Aug 2026, 08:28 UTC@iamkchelovek/5533 · this entry7 Aug 2026, 08:28 UTC1.00under a minute
@bogdanoffinvest/122217 Aug 2026, 08:43 UTC@iamkchelovek/5534 · this entry7 Aug 2026, 08:43 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@bogdanoffinvest7 (7/7 hand-verifiable sample passed)1.00under a minute@bogdanoffinvest (61)

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. 5 of the 6 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 22 comparable posts for this entry, running 28 July 2026 to 7 August 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 @bogdanoffinvest. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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

18,07720,50219,289.57 August 2026 — 18,077 subscribers7 August 2026 — 18,077 subscribers8 August 2026 — 18,820 subscribers8 August 2026 — 19,722 subscribers9 August 2026 — 20,502 subscribers11 August 2026 — 20,429 subscribers12 August 2026 — 20,384 subscribers13 August 2026 — 20,342 subscribers20,3427 August 202613 August 2026
8 measurements spanning 6 days, net +2,265. 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 17,713–20,866 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:0920,342-42
12 Aug 2026, 03:3220,384-45
11 Aug 2026, 02:2820,429-73
9 Aug 2026, 23:3320,502+780
8 Aug 2026, 22:2219,722+902
8 Aug 2026, 01:0318,820+743
7 Aug 2026, 07:0018,077no change
7 Aug 2026, 06:5318,077first reading

Engagement

30 posts held, back to 28 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 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
43.8%
avg views ÷ 20,342 subscribers
Avg views / post
8,910
30 posts measured
Reaction rate
1.17%
reactions ÷ views · ER floor
Posts in window
30
of 30 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. It is computed over the 27 of 30 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held30 (28 July 202612 August 2026)
Views total267,290
Reactions total2,950
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 23:25 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.

Reaction mix

2,950 reactions across 27 posts, in 8 distinct kinds. The most used accounts for 21.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁61921.0%
🔥59720.2%
58319.8%
👍55818.9%
😱1555.25%
😢1545.22%
👎1495.05%
💩1354.58%

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

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

12 Aug 2026, 08:37 UTC≈3,360 viewsread 12 August 2026
Photo

🔤 Юань-Рубль 🟢 Так же вчера на 5-минутке показывал, что у нас есть слом локального тренда, после его цена вернулась на тест пробитой линии. Но у нас так же есть и вот такая наклонка, которая еще не сломана. При этом по RSI есть треугольник из которого вышли вниз. 🚗 Существует ли треугольник по RSI? Если да, то цена должна скатываться, но пока мы этого не видим. Предполагаю слом наклонной линии, и поход в коррекцию

12 Aug 2026, 08:24 UTC≈3,470 viewsread 12 August 2026
Photo

🏦 Индекс Мосбиржи 🟢Вчера рисовал возможную вторую вершину в индексе, сегодня с утра получили её, с выносом на локальный перехай. но обе вершины - это, по сути, боковик. Боковик может быть как лонговый, так и шортовый. Учитывая настроения на рынке, ожидания прилета Уиткоффа и Кушнера, боковик может быть разгрузочным. В случае коррекции, тогда могли бы протестировать выход из треугольника, который образовался ранее.

11 Aug 2026, 11:54 UTC≈8,200 views138 reactionsread 12 August 2026
Photo

🏦 Индекс Мосбиржи 🟢 В индексе нарисовали точно такую же фигуру, как и в валюте. 🚗 По аналогии жду точно такое же движение, с формированием бычьей ловушки. Нефть сейчас слила весь сегодняшний рост. #индекс #индексмосбиржи #ммвб #irus #mxi #mix #imoexf #bogdanoffinvest $MXU6 $MXZ6 $MMU6 $MMZ6 $IMOEXF

🔥3629😁26👍25👎8💩6😱6😢2

11 Aug 2026, 11:13 UTC≈7,930 views91 reactionsread 12 August 2026

обновил логику прокси для защиты от РКН: 🟢ПК/Android: tg://proxy?server=150.241.113.52&port=443&secret=eec4e4e5f6b16f88d8525e3a6f145025b07777772e636c6f7564666c6172652e636f6d 🟢iPhone: tg://proxy?server=150.241.113.52&port=1443&secret=ddf49b894276655cde4fef5d93cd04ac64

🔥21👍2016😁15😢7😱6👎3💩3

9 Aug 2026, 09:32 UTC≈8,800 views108 reactionsread 12 August 2026

🔔 Корпоративные события на предстоящей неделе 10.08.2026 - ПОНЕДЕЛЬНИК ©️#T Т-технологии заседание СД. в повестке вопрос дивидендов за 1 полугодие 2026 г, закрытие реестра по дивидендам 4.6 руб (дивгэп ) ©️#AKRN Акрон закрытие реестра по дивидендам 235 руб (дивгэп) ©️#RUAL Русал СД по дивидендам за 1 п 2026 года 11.08.2026 - ВТОРНИК ©️#T Т-технологии финансовые результаты по МСФО за 2к 2026 года, онлайн-конференция

24👍24🔥21😁20😢7💩5👎4😱3

9 Aug 2026, 08:51 UTC≈9,190 views99 reactionsread 12 August 2026
Photo

📣 Новостной фон на день воскресенья: ❗️ Уиткофф и Кушнер могут посетить Киев и Москву на следующей неделе, — СМИ со ссылкой на источник ❗️ «Я не уверен, что война окончится скоро и я боюсь, что впереди тяжелая зима как для Украины, так и для всех нас. Я не вижу пути для скорого окончания войны», — Вучич после разговора с Зеленским. ❗️ Украина не собирается просто уходить из Донбасса или отдавать своих людей, — Зел

25👍22😁19🔥12💩7😢5😱5👎4

8 Aug 2026, 09:31 UTC≈9,030 views122 reactionsread 12 August 2026
Photo

☺️ Добрый день! Новостной фон на день субботы: ❗️ Сенат США одобрил законопроект об ужесточении американских санкций против России и Ирана. Теперь документ отправляется в Палату представителей. 🏠 Экспорт иранской нефти почти остановился из-за давления США, — Financial Times. 🏠 CША и Иран в ближайшее время, возможно 7 или 8 августа, заключат новое мирное соглашение, — министр финансов США Бессент. ❗️ Возгорание пр

👍29😁25🔥2421😢10👎8💩3😱2

7 Aug 2026, 11:33 UTC≈8,880 views104 reactionsread 12 August 2026
Photo

🏦 СБЕР ⛽️ Лукойл ⛽️ Газпром 🟢Как бы индекс не выглядел страшно, не стоит забывать, что после импульса в основных китах коррекция проходит в боковике, что подразумевает под собой в будущем продолжение роста после накопления. 🚗 Так что к текущей коррекции в индексе нужно относиться со скепсисом. Возможно, проявление слабости индекса только вызовет ускоренное налипание шорта, что в итоге послужит причиной выхода вве

😁2621👍20🔥18😱9👎5😢5

7 Aug 2026, 08:43 UTC≈8,910 views132 reactionsread 12 August 2026
Photo

🏦 Индекс Мосбиржи 🟢 Вчера индекс был слаб, но красную линию удержал. Сегодня новый удар в красную линию тренда, и от нее отскок как вчера. Рост в основном за счет роста валюты. Новостей нет, нефть в нуле 🟢 Сегодняшнее закрытие будет решающим для настроений следующей недели: ©️если обновим вчерашний хай, то может начаться шорт-сквиз в любой момент, т.к. шортов в рынке много ©️если закроемся на красной линии, то внов

31👍26😁25🔥22😢9👎7😱7💩5

7 Aug 2026, 08:28 UTC≈8,980 views114 reactionsread 12 August 2026
Photo

🔤 Юань-Рубль 🟢Юань пробил сегодня сопротивление 12,12. Данное сопротивление достаточно сильное. А так же вышел из клина вверх с ускорением. Каждый раз, когда валютная пара отрывалась от желтой линии тренда, то она к ней возвращалась, жду этого возврата и сейчас. Ускорение при перекупленности по RSI скорее намекает на завершение растущего тренда, но надо в финале получить разворотную свечку или сетап, как это было на

😁30🔥2518👍18😱9💩6👎5😢3

7 Aug 2026, 04:02 UTC≈9,520 views104 reactionsread 12 August 2026
Photo

☺️ Доброе утро! Новостной фон: ❗️ Трамп: ©️Нам ракеты Patriot тоже нужны. Байден дал Зеленскому и так много. ©️В вопросе урегулирования конфликта между РФ и Украиной достигнут прогресс ©️Пролив сейчас "в какой-то степени" сейчас открыт. ©️Я участвую в переговорах с Ираном. У нас все хорошо. Сделка может быть заключена в ближайшее время. 🏠 Посольство Ирана в Гане: «Для США остаeтся только один приемлемый исход: ПОЛН

23👍18🔥17😁17👎9😱8💩6😢6

6 Aug 2026, 10:32 UTC≈9,060 views122 reactionsread 12 August 2026
Photo

Рунет умер — пользователи массово сообщают о сбоях приложений и сайтов Ozon, WB, MAX, Яндекса, Авито, Т-Банка, Газпромбанка, РЖД, Ростелекома, массово жалуются россияне. 🚗 У меня Т-инвестиции с телефона работают, а с ПК — нет

25👍25🔥24😁18😱11😢9💩7👎3

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

Citation-graph rank

Citation-graph rank — 1,008,708 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“Sikorsky Trade | Трейдинг, инвестиции в криптовалюты, акции и IPO” (@iamkchelovek), 20,342 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/iamkchelovek.

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.