Telegram RegisterThe public register of Telegram

Channel

Грид боты и СВГ Ассистент |Юрий Гольчиков

@GridBot_SVG

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

2,004subscribers

-1 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-1001239997340
TypeChannel
Username@GridBot_SVG
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 live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/GridBot_SVG

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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
@obu4enie_treidingu/115710 Jul 2026, 07:09 UTC@GridBot_SVG/997 · this entry10 Jul 2026, 08:10 UTC1.0061 minutes
@obu4enie_treidingu/115814 Jul 2026, 08:11 UTC@GridBot_SVG/998 · this entry14 Jul 2026, 09:12 UTC1.0061 minutes
@obu4enie_treidingu/116020 Jul 2026, 07:10 UTC@GridBot_SVG/1000 · this entry20 Jul 2026, 08:11 UTC1.0061 minutes
@obu4enie_treidingu/116121 Jul 2026, 10:15 UTC@GridBot_SVG/1001 · this entry21 Jul 2026, 11:14 UTC1.0059 minutes
@GridBot_SVG/1006 · this entry24 Jul 2026, 08:36 UTC@obu4enie_treidingu/116624 Jul 2026, 09:12 UTC1.0036 minutes
@obu4enie_treidingu/116831 Jul 2026, 13:24 UTC@GridBot_SVG/1008 · this entry31 Jul 2026, 16:18 UTC1.002.9 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@obu4enie_treidingu12 (8/8 hand-verifiable sample passed)1.0061 minutes@obu4enie_treidingu (102)

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 10 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 13 comparable posts for this entry, running 9 July 2026 to 5 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 @obu4enie_treidingu. 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

2,0042,0052,004.57 August 2026 — 2,005 subscribers7 August 2026 — 2,005 subscribers11 August 2026 — 2,004 subscribers7 August 202611 August 2026
3 measurements spanning 3 days, net -1. 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,004–2,005 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 00:342,004-1
7 Aug 2026, 23:262,005no change
7 Aug 2026, 16:472,005first reading

Engagement

14 posts held, back to 9 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.2%
avg views ÷ 2,004 subscribers
Avg views / post
264
11 posts measured
Reaction rate
1.58%
reactions ÷ views · ER floor
Posts in window
11
of 14 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 5 August 2026
Posts held14 (9 July 20265 August 2026)
Views total2,908
Reactions total46
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:47 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
18m 31s
Average length
18m 31s

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

60 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 70.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4270.0%
👍1423.3%
46.67%

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

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

5 Aug 2026, 08:10 UTC117 views2 reactionsread 7 August 2026
Video

🚀 Отработка из конструктора сигналов по стратегии Памп+Разворотная свеча Подробнее о конструкторе сигналов писали тут https://t.me/obu4enie_treidingu/1157

👍2

1 Aug 2026, 07:09 UTC232 views1 reactionsread 7 August 2026
Photo

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

🔥1

31 Jul 2026, 16:18 UTC189 views3 reactionsread 7 August 2026
Photo

🔥 Пришёл отзыв после прошлого вебинара Ольга рассказала, что после практики у неё изменилось отношение к давнему конфликту с коллегой: «Я перестала прокручивать эту ситуацию в голове и задавать себе вопрос: “Почему так произошло?” Сейчас я спокойно об этом думаю - можно сказать, что вообще не думаю. Как-то всё отпустило». Представьте, сколько внутреннего ресурса раньше уходило на эти постоянные мысли, обиду и попыт

👍3

27 Jul 2026, 16:19 UTC289 views5 reactionsread 7 August 2026
Photo

🔥 Такое бывает редко: открываем бесплатный тест-драйв Grid Family Только с 27 июля по 2 августа вы сможете не просто узнать о системе, а попробовать её в работе вместе с нашими экспертами. За время тест-драйва вы: ✅ запустите Grid-ботов вместе с командой; ✅ познакомитесь с основами системного трейдинга на практике; ✅ получите помощь с регистрацией на бирже, если начинаете с нуля; ✅ разберётесь, как безопасно пополн

🔥31👍1

24 Jul 2026, 08:36 UTC338 views4 reactionsread 7 August 2026
Photo

🖥️ Запись вчерашнего вебинара 👉 https://paretoinvest.ru/sabotage Чувствуешь, что в трейдинге будто уперся в невидимый потолок или топчешься на месте 50/50, несмотря на крутую стратегию? Дело не в рынке, а в том, кто реально жмет на кнопки. Вот почему тебе нужно это посмотреть: ✅ Твой мозг тебя обманывает. Подсознание мощнее сознания в 275 000 раз. Пока ты анализируешь график, твой «внутренний компьютер» уже принял

2👍2

23 Jul 2026, 14:17 UTC308 views1 reactionsread 7 August 2026
Voice message

‼️ Мы подготовили абсолютно новую тему - без повторяющихся слайдов и без продаж. Поговорим о том: - какие внутренние установки могут блокировать результаты; - как автоматические реакции влияют на трейдинг, инвестиции и жизнь; - почему мы иногда сами саботируем решения, даже когда знаем, как правильно; - что показывают последние исследования; - какие выводы мы получили после собственных экспериментов. И самое главно

1

23 Jul 2026, 08:11 UTC269 views6 reactionsread 7 August 2026
Video message

Video message, posted without a caption

🔥6

22 Jul 2026, 14:17 UTC276 views4 reactionsread 7 August 2026
Photo

‼️ Завтра проведём вебинар: «Трейдинг без внутреннего саботажа» Он для тебя, если ты: - знаешь правила, но регулярно их нарушаешь; - закрываешь прибыль слишком рано; - не можешь спокойно пережить убыток; - постоянно проверяешь рынок; - после одной ошибки теряешь контроль; - понимаешь, что проблема уже не в знаниях. На вебинаре разберём не очередную стратегию входа, а то, что происходит внутри трейдера до, во время

🔥4

21 Jul 2026, 11:14 UTC259 views9 reactionsread 7 August 2026

🧪🔬 Мы провели эксперимент с фокус-группой среди учеников - и получили неожиданные результаты. Мы взяли новую для нас тему, о которой раньше почти не говорили, и предложили ребятам поработать не с очередной стратегией, а с внутренними сценариями и реакциями. Результаты начали проявляться уже в первые дни: - стало меньше тревоги во время сделки; - исчезло желание постоянно проверять рынок; - стало проще следовать св

🔥9

20 Jul 2026, 08:11 UTC262 views8 reactionsread 7 August 2026

💡 Трейдинг без внутреннего саботажа: разбираем блоки, которые сливают депозит Можно знать все правила трейдинга. Соблюдать риск-менеджмент. Ждать подтверждения, не входить на эмоциях и даже вести дневник сделок. Но почему тогда на дистанции результат всё равно уходит в минус? Иногда дело не в знаниях и не в стратегии. А в скрытых сценариях, которые включаются в момент сделки: - желание быстрее отыграться; - страх

🔥8

14 Jul 2026, 09:12 UTC369 views3 reactionsread 7 August 2026
Photo

🚀 EVAA: +22.55% за 23 часа на 2-м плече Недавно пришел сигнал по EVAA: на входе был импульсный памп +241.75% на 4h, а на 2-м плече сделка закрылась в плюс +22.55% всего за 23 часа 4 минуты. На скринах видно и сам сигнал, и итог по сделке. И вот здесь как раз наша сильная сторона: мы не берем каждый памп подряд. Мы выцепляем только те движения, где после сильного импульса рынок уже начинает показывать готовность к

👍3

10 Jul 2026, 08:10 UTC386 views4 reactionsread 7 August 2026
Photo

🟥 Конструктор сигналов: из чего собираются свои связки 🌐 Конструктор сигналов - это не одна готовая схема, а набор элементов, из которых можно собрать свою логику входа под конкретную задачу. На скрине как раз видно, из чего можно собирать сигналы: цена, объем, RSI, SMA, EMA, MACD, Stochastic, ATR, Alligator, Funding, OI, Bollinger, Profile, CMC Rank, свечные паттерны, дивер. То есть можно собрать не просто “сигна

🔥3👍1

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

“Грид боты и СВГ Ассистент |Юрий Гольчиков” (@GridBot_SVG), 2,004 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/GridBot_SVG.

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.