J64-HYC-HTD JRR-7YA-CCC VMG-HXK-VAL FCX-P94-JCV https://www.bungie.net/7/ru/codes/redeem
❤31🔥3custom 53166794309097325213👏1

Channel
@destiny2news
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Cite this entry
3,987subscribers
-171 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001706316149 |
|---|---|
| Type | Channel |
| Username | @destiny2news |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/destiny2news |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 17:09 | 3,987 | -11 |
| 12 Nov 2026, 21:21 | 3,998 | -4 |
| 8 Nov 2026, 16:11 | 4,002 | -1 |
| 5 Nov 2026, 06:06 | 4,003 | +1 |
| 30 Oct 2026, 05:36 | 4,002 | -7 |
| 27 Oct 2026, 09:56 | 4,009 | -1 |
| 24 Oct 2026, 00:55 | 4,010 | -21 |
| 21 Oct 2026, 08:11 | 4,031 | -4 |
| 18 Oct 2026, 01:37 | 4,035 | -2 |
| 14 Oct 2026, 19:48 | 4,037 | -3 |
| 11 Oct 2026, 15:37 | 4,040 | -1 |
| 5 Oct 2026, 08:15 | 4,041 | -2 |
| 26 Sept 2026, 21:00 | 4,043 | +5 |
| 17 Sept 2026, 14:16 | 4,038 | -10 |
| 13 Sept 2026, 15:37 | 4,048 | -6 |
| 9 Sept 2026, 18:17 | 4,054 | -3 |
| 4 Sept 2026, 21:17 | 4,057 | -9 |
| 1 Sept 2026, 15:27 | 4,066 | -11 |
| 29 Aug 2026, 13:17 | 4,077 | -17 |
| 26 Aug 2026, 07:48 | 4,094 | first reading |
16 posts held, back to 9 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pages 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 16 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.
770 reactions across 16 posts, in 20 distinct kinds. The most used accounts for 23.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 184 | 23.9% | |
| ❤ | 179 | 23.2% | |
| custom 5316679430909732521 | 101 | 13.1% | |
| 🤡 | 97 | 12.6% | |
| 😁 | 59 | 7.66% | |
| custom 5778476195771323325 | 46 | 5.97% | |
| 😭 | 43 | 5.58% | |
| ⚡ | 9 | 1.17% | |
| 👍 | 8 | 1.04% | |
| 🤗 | 8 | 1.04% | |
| 🫡 | 8 | 1.04% | |
| 🏆 | 7 | 0.909% | |
| custom 5312211320597128165 | 5 | 0.649% | |
| 💯 | 5 | 0.649% | |
| 🤔 | 3 | 0.39% | |
| 🦄 | 3 | 0.39% | |
| 👏 | 2 | 0.26% | |
| 🎉 | 1 | 0.13% | |
| 🗿 | 1 | 0.13% | |
| 🤬 | 1 | 0.13% |
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 16 of the 16 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 770 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 9 June 2026 to 9 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 @destiny2news. 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 16 most recent posts we hold for this entry, published 9 June 2026 to 9 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.
J64-HYC-HTD JRR-7YA-CCC VMG-HXK-VAL FCX-P94-JCV https://www.bungie.net/7/ru/codes/redeem
❤31🔥3custom 53166794309097325213👏1
Пришла пора закидать помидорами главного босса 🔪 https://petecarsons.com
😁27💯4❤1🎉1
9NG-KDD-PNG 7LD-PLJ-FN3 https://www.bungie.net/7/ru/codes/redeem
❤24custom 53166794309097325212
F6K-D44-JH4 https://www.bungie.net/7/ru/codes/redeem
😁17❤16🤔2💯1custom 53166794309097325211
Сегодня Bungie сообщили об очередном сокращении сотрудников студии 😭 Основная часть сокращений коснется конечно же команды Destiny 2, но так же некоторых сотрудников Marathon
😭43custom 531667943090973252116🤡8❤3👍2👏1🤔1
🤩🤩🤩🤩🤩🤩🤩🤩 У игроков с русским регионом в ПСН вновь появился доступ к Destiny 2 😳 Для того чтобы войти со своего аккаунта вам потребуется настроить DNS на вашей консоли. Неожиданно, но приятно ❤️
🔥58🤡8⚡5custom 53166794309097325212🤗1🤬1
😄 Приглашаем на сервер DUST | Destiny 2 & Arc Raiders 🌈 Мы расширили направление сервера и теперь набираем людей не только в Destiny 2, но и в ARC RAIDERS. DUST остаётся одним из самых активных русскоязычных сообществ по Destiny 2, а теперь мы развиваем и направление ARC. О нас: 💖 Прайм-тайм: 18:00–01:00 (МСК) 💖 Удобный сервер с ботами и полезностями. Сервер улучшается и адаптируется под пользователей. 💖 Помощь с …
🤡27❤12custom 53122113205971281654🦄3⚡2🔥1
⚡ Полезно для игроков Destiny 2 Если вы играете с друзьями на других серверах или периодически сталкиваетесь с ошибкой Tapir, можно попробовать LagoFast. Что может быть полезно: 🔹 Ускорение между регионами и оптимизация маршрутов для снижения задержки; 🔹 Помощь в исправлении ошибки Tapir и других проблем с подключением; 🔹 Дополнительные игровые инструменты для более комфортной игры. 🚀 Бесплатно попробовать LagoFast…
🤡40custom 53166794309097325219👍3❤1custom 53122113205971281651custom 57784761957713233251
Небольшие изменения во вторник
❤11😁8🤡2custom 53166794309097325211
FREE COSMETICS: Destiny 2 - Deadlands Bundle Мертвые земли Орнамент брони Титана: 3TG-G67-PYD Мертвые земли Орнамент брони Варлока: MMX-3HF-CJ4 Мертвые земли Орнамент брони Охотника: 6MC-A3F-X3R Полевой Стенограф Оболочка Призрака: FPP-NHV-HNC Мобильный массив Сперроу: 7AM-PJR-GMX Динамическая эквивалентность Корабль: K9P-PVD-NR6 Вечный скакун (фото 4) Сперроу: M3L-7DA-67C Горячее и холодное (фото 3) шейдер: FLK-TX…
❤21🔥3custom 53166794309097325213🤡1
Вчера на всех платформах в игру зашло 385к стражей ❤️ Интересный факт, на старте Destiny 2 в игру зашло 3.8 миллиона человек. Статистику можно посмотреть тут ❤️
🔥63🏆7custom 53166794309097325215🤗4❤1
Детектив Пикачу ведёт расследование 👀
custom 531667943090973252122🤡3😁3🗿1custom 57784761957713233251
Showing the 12 most recent of 16 posts we hold for @destiny2news. 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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“Destiny 2 News” (@destiny2news), 3,987 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/destiny2news.
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.