Channel
@ydrmain
On this record: Growth · Engagement · Posts · Citations · Cite this entry
537subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001375589080 |
|---|---|
| Type | Channel |
| Username | @ydrmain |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/ydrmain |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 22:28 | 537 | -2 |
| 7 Aug 2026, 11:21 | 539 | no change |
| 7 Aug 2026, 00:47 | 539 | first reading |
20 posts held, back to 16 September 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 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 20 posts for this entry, the most recent from 8 June 2023. An engagement rate over an empty window would be a number about nothing.
Ryders🐉! 💥$NGI IMO is now live on https://ydragon.io 💥 1. As soon as you click ‘buy’, index tokens will be added to your wallet after you accept the transaction (but tokens will not be transferrable until IMO ends). 2. Index price will be set to $1 initially. 3. During the IMO there will be a 0% minting fee. Once the IMO period has ended, you can still buy (mint) the index but the minting fee will be 0.5%. Read mo…
YDragon - DeFi made simple pinned a photo
Ryders🐉, 💥BSC Next-Gen Index ($NGI) Launch💥 The $NGI IMO will be live at ydragon.io this Thursday, 8th June @ 2pm UTC! The IMO will last 48 hours and during this period investors can benefit from 0 fees! Read more about the $NGI index and IMO here: https://medium.com/ydragon-io/embrace-the-world-of-ai-through-this-index-bd3dba38de75 Yield to the mighty
YDragon - DeFi made simple pinned «100m YDR tokens have just been burnt on Ethereum. 75m YDR burn TX https://etherscan.io/tx/0x7d107870407f0e865a3e94e1d6590495be6f7b6f4e0f6ffe21d3607947c4d525 25m YDR burn TX https://etherscan.io/tx/0x1b478ef808d8b4a52a69ca65ca6aad9ed0fb30c02bf472d202082f21758e9584»
100m YDR tokens have just been burnt on Ethereum. 75m YDR burn TX https://etherscan.io/tx/0x7d107870407f0e865a3e94e1d6590495be6f7b6f4e0f6ffe21d3607947c4d525 25m YDR burn TX https://etherscan.io/tx/0x1b478ef808d8b4a52a69ca65ca6aad9ed0fb30c02bf472d202082f21758e9584
YDragon - DeFi made simple pinned a photo
The second YDR burn will be happening this coming Friday, March 31st at 2pm UTC. 100,000,000 $YDR tokens (22.22% of current total supply) will be burnt on Ethereum.
First $YDR burn event of 50,000,000 tokens has occurred. https://etherscan.io/tx/0xf487edba00a3f088b70d977a16fd57264735da42675b7a433c633331135e043d
Ryders🐉 50,000,000 $YDR tokens are about to be burned in less than 30 minutes.
YDragon - DeFi made simple pinned a photo
Happy New Year Ryders🐉 The new year brings hope for a better future and we're unleashing the dragon's first new year's resolution. YDragon is currently focusing on a vital goal for 2023: the long-term sustainability of the project. That is why we have decided to start burning $YDR. Today, we are announcing the first of many burns: 50,000,000 $YDR tokens (10% of the total supply) will be burnt on 20th January 2023 …
Ryders🐉, Just here with a short dev update. As you probably have already noticed we've slowed down operations, mainly to conserve funds to survive the current bear market. The hope is that once market conditions change soon we can then resume operating as usual before. Expanding the YDragon ecosystem to other chains has been put on hold for now. We will continue to work on releasing new innovative indexes on the cu…
Showing the 12 most recent of 20 posts we hold for @ydrmain. 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.
Citation-graph rank — 850,455 of 1,480,975entries 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“YDragon - DeFi made simple” (@ydrmain), 537 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/ydrmain.
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.