Telegram RegisterThe public register of Telegram
Telegram profile photo for MetaDragon News

Channel

MetaDragon News

@MetaDragonNews

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

304subscribers

-17 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001682770018
TypeChannel
Username@MetaDragonNews
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 October 2026
Last confirmed live12 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/MetaDragonNews

Topic

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 8 October 2026 and assigned it the closest of 31 fixed categories, at 93% 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.

Growth

304321312.57 August 2026 — 321 subscribers15 August 2026 — 319 subscribers23 August 2026 — 315 subscribers8 September 2026 — 311 subscribers16 September 2026 — 309 subscribers1 October 2026 — 306 subscribers8 October 2026 — 306 subscribers12 October 2026 — 304 subscribers7 August 202612 October 2026
8 measurements spanning 66 days, net -17. 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 301–324 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 02:57304-2
8 Oct 2026, 03:22306no change
1 Oct 2026, 05:55306-3
16 Sept 2026, 13:16309-2
8 Sept 2026, 18:55311-4
23 Aug 2026, 21:09315-4
15 Aug 2026, 10:26319-2
7 Aug 2026, 12:20321first reading

Engagement

20 posts held, back to 29 May 2024 — 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 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

8 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 62.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍562.5%
❤112.5%
🔥112.5%
😁112.5%

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 4 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 8 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 29 May 2024 to 20 June 2024, 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

20 Jun 2024, 09:19 UTC193 views3 reactionsread 8 October 2026
Photo

Announcement: META Rewards Has Been Airdropped Dear META Community, we have several important announcements: 1. An additional META airdrop has been sent to the wallets of the top 200 players from Arena Season 2. Please check your wallets promptly. 2. The MDS Quiz Collectibles DApp will be closed on June 21. Please withdraw your assets from your backpack in a timely manner. 3. Starting tomorrow, we will be handlin…

👍2❤1

19 Jun 2024, 04:33 UTC176 views1 reactionsread 8 October 2026
Photo

MetaDragon Important Notice Dear MetaDragon community, thank you for your endless support to MetaDragon through this hard times, we have several important announcements : 1. MWars Arena seasonal rank has been announced, please check list of winners here : https://metadragon.gitbook.io/en/events/mwars-pvp/june Congratulations to Lord of MetaDragons who made it to the top! We'll be distributing airdrop rewards tomor…

👍1

18 Jun 2024, 03:44 UTCviews —

MetaDragon News pinned «Announcement: Future Arrangements for MWars Since $META was unfortunately attacked by hackers, we have suffered a significant blow and caused inconvenience to everyone. We deeply apologize for this! Here are the upcoming arrangements: - On June 19th, second…»

18 Jun 2024, 03:44 UTC133 views1 reactionsread 8 October 2026

Announcement: Future Arrangements for MWars Since $META was unfortunately attacked by hackers, we have suffered a significant blow and caused inconvenience to everyone. We deeply apologize for this! Here are the upcoming arrangements: - On June 19th, second season of MWars will come to an end. Afterward, operations will be halted, and we will enter a phase of technical maintenance. - On June 20th, top 200 players…

🔥1

3 Jun 2024, 07:12 UTC143 views3 reactionsread 8 October 2026

Announcement: Subsequent Arrangements for META and MWars Recently, $META contract was hacked, and we deeply apologize for the inconvenience caused! We are very grateful for the understanding shown by some of our partners and major stakeholders! Note: Currently, the NFT contract still has security vulnerabilities. Please do not mint NFTs. In the face of this severe setback, we are actively communicating and handling…

👍2😁1

3 Jun 2024, 07:12 UTC118 viewsread 8 October 2026

Announcement: MWars May Legion Ranking Rewards have been airdropped. Due to $META contract being hacked and the resulting security risks to assets, Legion ranking rewards will no longer be set starting from June. After the second season of Arena ends, additional META airdrop will be given according to the seasonal leaderboard rankings.

1 Jun 2024, 11:14 UTC131 viewsread 8 October 2026

Announcement:META NFTs stolen by hackers have been compensated. Dear Community, META and BNB compensation for lost META NFTs has been successfully airdropped to the respective wallet addresses. If you have not received your compensation, please fill out the form here :forms.office.com/r/gnKd1ijmup Thank you for your continued support in this hard time. Best regards, MetaDragon Team.

31 May 2024, 08:24 UTCviews —

MetaDragon News pinned «Announcement: Legion Season Rewards Dear MetaDragon community, attached are some important announcement regarding Legion leaderboard rewards. Today marks the final day for May Legion ranking rewards. Top 30 members will be receiving airdrops as promised…»

31 May 2024, 08:24 UTC129 viewsread 8 October 2026

Announcement: Legion Season Rewards Dear MetaDragon community, attached are some important announcement regarding Legion leaderboard rewards. Today marks the final day for May Legion ranking rewards. Top 30 members will be receiving airdrops as promised : https://metadragon.gitbook.io/en/events/mwars-legion Please note that there will be no legion awards set for June. Legion points will continue as usual. Thank y…

30 May 2024, 09:52 UTCviews —

MetaDragon News pinned «Dear META Community Members, The recent hacking incident has brought about many issues, and we will actively communicate and address them! Firstly, we would like to remind you that the NFT contract remains insecure. Please refrain from minting NFTs. After…»

30 May 2024, 09:52 UTC97 viewsread 8 October 2026

Dear META Community Members, The recent hacking incident has brought about many issues, and we will actively communicate and address them! Firstly, we would like to remind you that the NFT contract remains insecure. Please refrain from minting NFTs. After preliminary assessment and communication, over 4000 NFTs were compromised in this hacking incident. After deducting portions allocated to the META fund and marke…

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

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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“MetaDragon News” (@MetaDragonNews), 304 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/MetaDragonNews.

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.