Channel
@MongoDBRussian
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
244subscribers
-9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001352542521 |
|---|---|
| Type | Channel |
| Username | @MongoDBRussian |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/MongoDBRussian |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 09:36 | 244 | -4 |
| 4 Sept 2026, 17:17 | 248 | -1 |
| 20 Aug 2026, 15:02 | 249 | -1 |
| 14 Aug 2026, 11:37 | 250 | -3 |
| 8 Aug 2026, 09:19 | 253 | no change |
| 7 Aug 2026, 16:39 | 253 | first reading |
20 posts held, back to 27 June 2022 — 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 22 July 2026. An engagement rate over an empty window would be a number about nothing.
44 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 59.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 26 | 59.1% | |
| ❤ | 7 | 15.9% | |
| 👏 | 5 | 11.4% | |
| 🤔 | 3 | 6.82% | |
| 😁 | 2 | 4.55% | |
| 🔥 | 1 | 2.27% |
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 17 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 44 reactions 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 27 June 2022 to 22 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MongoDBRussian. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 27 June 2022 to 22 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
8.3.7 (Jul 17) ◦ 8.2.12 (Jun 26) ◦ 8.0.28 (Jul 16) ◦ 7.0.39 (Jul 16) Вышли новые версии 8.3.7, 8.2.12, 8.0.28 и 7.0.39 • Документация • Бесплатные курсы в MongoDB University • Англоязычная группа: @mongo_db • Песочница: play.db-ai.dev • 🧑🔧 Консультации и поддержка MongoDB от 2190€ в месяц: @dd_bb Stable: 8.3.7 (Jul 17) ◦ 8.2.12 (Jun 26) Major: 8.0.28 (Jul 16) Bugfix: 7.0.39 (Jul 16) ☠️ EOL: 6.0.29 (Jun 10) ◦ 5.0…
❤2😁1
8.3.4 (Jun 10) ◦ 8.2.11 (Jun 10) ◦ 8.0.26 (Jun 10) ◦ 7.0.37 (Jun 10) Вышли новые версии 4.4.31 • Документация • Бесплатные курсы в MongoDB University • Англоязычная группа: @mongo_db • Песочница: play.db-ai.dev • 🧑🔧 Консультации и поддержка MongoDB от 2190€ в месяц: @dd_bb Stable: 8.3.4 (Jun 10) ◦ 8.2.11 (Jun 10) Major: 8.0.26 (Jun 10) Bugfix: 7.0.37 (Jun 10) ☠️ EOL: 6.0.29 (Jun 10) ◦ 5.0.34 (Jun 10) ◦ 4.4.31 (J…
👏1
8.3.4 (Jun 10) ◦ 8.2.11 (Jun 10) ◦ 8.0.26 (Jun 10) ◦ 7.0.37 (Jun 10) Вышли новые версии 8.3.4, 8.2.11, 8.0.26, 7.0.37, 6.0.29 и 5.0.34 • Документация • Бесплатные курсы в MongoDB University • Англоязычная группа: @mongo_db • Песочница: play.db-ai.dev • 🧑🔧 Консультации и поддержка MongoDB от 2190€ в месяц: @dd_bb Stable: 8.3.4 (Jun 10) ◦ 8.2.11 (Jun 10) Major: 8.0.26 (Jun 10) Bugfix: 7.0.37 (Jun 10) ☠️ EOL: 6.0.2…
8.3.3 (May 21) ◦ 8.2.10 (May 21) ◦ 8.0.24 (May 21) ◦ 7.0.35 (May 21) Вышли новые версии 8.3.3, 8.2.10, 8.0.24 и 7.0.35 • Документация • Бесплатные курсы в MongoDB University • Англоязычная группа: @mongo_db • Песочница: play.db-ai.dev • 🧑🔧 Консультации и поддержка MongoDB от 2190€ в месяц: @dd_bb Stable: 8.3.3 (May 21) ◦ 8.2.10 (May 21) Major: 8.0.24 (May 21) Bugfix: 7.0.35 (May 21) ☠️ EOL: 6.0.28 (May 6) ◦ 5.0.…
8.3.2 (May 5) ◦ 8.2.9 (May 6) ◦ 8.0.23 (May 6) ◦ 7.0.34 (May 6) Вышли новые версии 8.3.2, 8.2.9, 8.0.23, 7.0.34, 6.0.28 и 5.0.33 • Документация • Бесплатные курсы в MongoDB University • Англоязычная группа: @mongo_db • Песочница: play.db-ai.dev • 🧑🔧 Консультации и поддержка MongoDB от 2190€ в месяц: @dd_bb Stable: 8.3.2 (May 5) ◦ 8.2.9 (May 6) Major: 8.0.23 (May 6) Bugfix: 7.0.34 (May 6) ☠️ EOL: 6.0.28 (May 6) ◦…
👏1
8.2.7 (Mar 30) ◦ 8.0.21 (Apr 8) ◦ 7.0.32 (Apr 13) Вышли новые версии 8.0.21 и 7.0.32 • Документация • Бесплатные курсы в MongoDB University • Англоязычная группа: @mongo_db • Песочница: play.db-ai.dev • 🧑🔧 Консультации и поддержка MongoDB от 2190€ в месяц: @dd_bb Stable: 8.2.7 (Mar 30) Major: 8.0.21 (Apr 8) Bugfix: 7.0.32 (Apr 13) ☠️ EOL: 6.0.27 (Dec 23 '25) ◦ 5.0.32 (Dec 23 '25) ◦ 4.4.30 (Dec 23 '25) ◦ 4.2.25 (…
❤1
8.2.7 (Mar 30) ◦ 8.0.20 (Feb 25) ◦ 7.0.31 (Feb 25) Вышла новая версия 8.2.7 • Документация • Бесплатные курсы в MongoDB University • Англоязычная группа: @mongo_db • Песочница: play.db-ai.dev • 🧑🔧 Консультации и поддержка MongoDB от 2190€ в месяц: @dd_bb Stable: 8.2.7 (Mar 30) Major: 8.0.20 (Feb 25) Bugfix: 7.0.31 (Feb 25) ☠️ EOL: 6.0.27 (Dec 23 '25) ◦ 5.0.32 (Dec 23 '25) ◦ 4.4.30 (Dec 23 '25) ◦ 4.2.25 (Dec 4 '2…
👍2
8.2.6 (Feb 25) ◦ 8.0.20 (Feb 25) ◦ 7.0.31 (Feb 25) Вышли новые версий 8.2.6, 8.0.20 и 7.0.31 • Документация • Бесплатные курсы в MongoDB University • Англоязычная группа: @mongo_db • Песочница: play.db-ai.dev 🧑🔧 Консультации и поддержка MongoDB от 2190€ в месяц: @dd_bb Stable: 8.2.6 (Feb 25) Major: 8.0.20 (Feb 25) Bugfix: 7.0.31 (Feb 25) ☠️ EOL: 6.0.27 (Dec 18 '25) ◦ 5.0.32 (Dec 17 '25) ◦ 4.4.30 (Dec 18 '25) ◦ 4…
👏1
8.2.5 (Feb 10) ◦ 8.0.19 (Feb 10) ◦ 7.0.30 (Feb 10) Вышли новые версий 8.2.5, 8.0.19 и 7.0.30 • Документация • Бесплатные курсы в MongoDB University • Англоязычная группа: @mongo_db • Песочница: play.db-ai.dev 🧑🔧 Консультации и поддержка MongoDB от 2190€ в месяц: @dd_bb Stable: 8.2.5 (Feb 10) Major: 8.0.19 (Feb 10) Bugfix: 7.0.30 (Feb 10) ☠️ EOL: 6.0.27 (Dec 23 '25) ◦ 5.0.32 (Dec 23 '25) ◦ 4.4.30 (Dec 23 '25) ◦ 4…
😁1
⚠️ CVE-2025-14847: уязвимость разжатия zlib, позволяющая читать неинициализированную память процесса mongod/mongos Затрагивает все версии начиная с 3.6 Достаточно сетевого доступа к mongodb, аутентификация не требуется — злоумышленник может отправить специально сформированный запрос и получить произвольные фрагменты памяти процесса (данные в кеше коллекций, переменные окружения, конфигурацию и т.д) Быстрое решение…
👍6❤1🤔1
8.0.6 (Mar 19) ◦ 7.0.18 (Mar 19) ◦ 6.0.21 (Mar 17) Выпущены новые версии 8.0.6, 7.0.18 & 6.0.12 с незначительными изменениями • Документация • Официальный курсы: MongoDB University • 🧑🔧 Консультации и поддержка MongoDB от 2190€ в месяц: @dd_bb • Песочница: play.db-ai.dev Stable: 8.0.6 (Mar 19) Bugfix: 7.0.18 (Mar 19) ◦ 6.0.21 (Mar 17)) Legacy: 5.0.31 (Jan '25, EOL Oct '24) EOL: ☠️ 4.4.29 (Feb '24) ◦ 4.2.24 (Ap…
🤔1
8.0.4 (Dec 9, '24) ◦ 7.0.16 (Dec 20, '24) ◦ 6.0.20 (Jan 15) 💀 В октябре 2024 завершилась поддержка ветки 5.0 • Документация • Официальный курсы: MongoDB University • 🧑🔧 Консультации и поддержка MongoDB от 2190€ в месяц: @dd_bb • Песочница: play.db-ai.dev Stable: 8.0.4 (Dec 9, '24) Bugfix: 7.0.16 (Dec 20, '24) ◦ 6.0.20 (Jan 15) Legacy: 5.0.31 (Jan '25, EOL Oct '24) EOL: ☠️ 4.4.29 (Feb '24) ◦ 4.2.24 (Apr '23) • L…
👏1🤔1
Showing the 12 most recent of 20 posts we hold for @MongoDBRussian. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Mongo Times” (@MongoDBRussian), 244 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/MongoDBRussian.
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.