Приятного просмотра 🙏🏻
Signed Сергей Малявка

Channel
@DaVinci_pro_magadan
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
6subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001474602708 |
|---|---|
| Type | Channel |
| Username | @DaVinci_pro_magadan |
| Description | Пусть РАБотает роБОТ, он железный) |
| Created | Between 1 April 2019 and 3 March 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/DaVinci_pro_magadan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 21:03 | 6 | no change |
| 7 Aug 2026, 09:26 | 6 | first reading |
20 posts held, back to 3 March 2020 — the 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 20 posts for this entry, the most recent from 20 June 2020. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
Приятного просмотра 🙏🏻
Signed Сергей Малявка
Прошел технический вебинар по обновлению DaVinci 2.0 Были разобраны все функции подробно. Отвечено на десятки вопросов на примере собственных счетов. Был затронут вопрос нейросетей с информацией от разработчиков. Советуем всем посмотреть: http://www.youtube.com/watch?v=T1XqcnwXMyk Если вы еще не подписаны на официальный техканал, то подписывайтесь: https://t.me/joinchat/AAAAAEUL_Qyt1vuYHShl5w
Signed Сергей Малявка
Приглашаем всех на техвебинар по обновлению: http://www.youtube.com/watch?v=T1XqcnwXMyk
Signed Сергей Малявка
✍ Запомни: Инвестируй только то, что готов потерять!
Signed Сергей Малявка
👍
Signed Сергей Малявка
Photo, posted without a caption
Signed Сергей Малявка
Техвебинар с обзором обновления DaVinci 2.0 будет сегодня 30 марта в 20:00 (МСК). В первую очередь будут рассмотрены вопросы из формы: https://docs.google.com/forms/d/1-RO-m7VqeaQBUAQOfIKbrHay3pkRnzPPkTCyoRygWl4/edit Создан официальных техканал, советуем всем подписаться. Ссылка на вебинар будет на техканале: https://t.me/joinchat/AAAAAEUL_Qyt1vuYHShl5w
Signed Сергей Малявка
Не рекомендуется запускать новую версию DaVinci 2.0 на парах, где открыты сделки по третьей сетке (System 3), открыты сделки руками или сторонними советниками. Пожалуйста, дождитесь техвебинара.
Signed Сергей Малявка
⚙️Друзья, в ближайшее время будет проведен технический вебинар. На нем мы подробно разберем обновление DaVinci 2.0. Ссылка и анонс будет на официальном канале (📌t.me/davinciproofficial). ❓Свои вопросы вы можете задать в google-форме: https://docs.google.com/forms/d/1-RO-m7VqeaQBUAQOfIKbrHay3pkRnzPPkTCyoRygWl4/edit Напоминаем, что подробная инструкция по обновлению есть в ваших личных кабинетах. Советуем ознакомитьс…
Signed Сергей Малявка
Ссылка на презентацию: http://www.youtube.com/watch?v=J9T41QkN97I
Signed Сергей Малявка
Начинаем продолжать)
Signed Сергей Малявка
Самая дорогая книга в мире — «Лестерский кодекс» Леонардо да Винчи. Он написан перевернутым шрифтом, поэтому читать ее можно только смотря через зеркальное отражение.
Signed Сергей Малявка
Showing the 12 most recent of 20 posts we hold for @DaVinci_pro_magadan. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“DaVinci.pro.49” (@DaVinci_pro_magadan), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/DaVinci_pro_magadan.
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.