Channel
@mega_connector
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
294subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001546400297 |
|---|---|
| Type | Channel |
| Username | @mega_connector |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/mega_connector |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 03:56 | 294 | -1 |
| 7 Aug 2026, 04:17 | 295 | no change |
| 7 Aug 2026, 04:04 | 295 | first reading |
15 posts held, back to 18 September 2025 — 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 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 15 posts for this entry, the most recent from 29 January 2026. An engagement rate over an empty window would be a number about nothing.
51 reactions across 6 posts, in 6 distinct kinds. The most used accounts for 51.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 26 | 51.0% | |
| 👌 | 11 | 21.6% | |
| 👍 | 8 | 15.7% | |
| ❤ | 3 | 5.88% | |
| 🎉 | 2 | 3.92% | |
| 👏 | 1 | 1.96% |
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 6 of the 15 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 51reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 18 September 2025 to 29 January 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.
И в старом и новом софте была проблема, что когда ПО запускаешь в 1 раз, то в настройках в разделе API указано не то что нужно. Из-за этого к боту не подключается прокладка для МТ4/5. Если столкнулись с похожей проблемой, то зайдите в пункт меню API и укажите в списке intrade_bar_console_bot
👌4👍2
Касательно обновления на 2 версию программы - всё еще в процессе. На данном моменте идет проработка нового интерфейса программы. Промежуточные макеты на скриншотах. Но какой-то MVP выйдет относительно скоро.
🔥11👌2
MegaConnector pinned a file
Версия 1.35.18b ℹ️ Продлена лицензия: до 2026.08.30 ℹ️ Бот скомпилирован на более свежем софте ℹ️ Исправлен баг: добавлено обновление для прокладки МТ4, устраняющее ошибку "indicator on custom buffer is not supported yet" 🟢Программа бесплатная (для REAL счета тоже). Подключаться к партнерской программе не нужно! Инструкция Пароль от архива: 12345
🔥7👌5🎉2👍2
MegaConnector pinned «Обновление прокладки для МТ4. Исправлена ошибка: indicator on custom buffer is not supported yet»
File, posted without a caption
🔥8👍1
Обновление прокладки для МТ4. Исправлена ошибка: indicator on custom buffer is not supported yet
❤2👍1👏1
Возможно стоит будет удалить папки __pycache__ в исходниках, если проблемы будут с установкой.
MegaConnector pinned a file
Бот моей разработки. Можете пользоваться и попытать удачу. Обновление по коннектору пока не готово, и я сейчас занят, придется ждать. P.S. брокер https://tradeup.net/
👍2❤1
Исходники для бота trade up. Третий раз они не вывели сумму в 50$. Так что смысла не вижу заморачиваться с ними. Как зарабатывать тогда? 1. Можете попробовать уложиться в два вывода. Вывести скажем на 50-100% больше с небольшой суммы. 2. Ну или продавать бота под видом работающего. Он же реально работает) Просто бабки сильно больше не вывести выше чем завел.
Как запустить бота 1. Настроить переменные окружения в .env, не все а вот эти: BROKER_ACCESS_TOKEN и BROKER_WS_COOKIES Пример: BROKER_ACCESS_TOKEN="115adaab-b59a-4c00-a023-09ac3ab2a570" BROKER_WS_COOKIES="multibrand_session=BnqUXIBB8hHWMtIXa0yGGAoc51lVNGK3dHxWS81" Взять эти куки и токен авторизации можно из http запросов или вебсокета прямо из отладки в браузере. Для этого нажмите F12, появится окно отладки. Пере…
Showing the 12 most recent of 15 posts we hold for @mega_connector. 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.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Какой рынок вам больше нравится?
The shares total 112%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Что больше нравится?
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 15 most recent posts we hold, published 18 September 2025 to 29 January 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 465,544 of 1,481,217entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“MegaConnector” (@mega_connector), 294 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/mega_connector.
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.