Telegram RegisterThe public register of Telegram
Telegram profile photo for Decenta Yield

Channel

Decenta Yield

@Dyield

On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

15subscribers

+1 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-1001760850899
TypeChannel
Username@Dyield
Created10 January 2022 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live6 October 2026
Measurements held3
Confirmed unchanged3 times, most recently 6 October 2026
On Telegramt.me/Dyield

Topic

Crypto & trading — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 90% 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

141514.57 August 2026 — 14 subscribers12 August 2026 — 14 subscribers13 September 2026 — 15 subscribers7 August 202613 September 2026
3 measurements spanning 37 days, net +1. 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 14–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 05:3815+1
12 Aug 2026, 01:0214no change
7 Aug 2026, 04:2214first reading

Engagement

5 posts held, back to 10 January 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 5 posts for this entry, the most recent from 25 March 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

25 Mar 2022, 11:20 UTC821 viewsread 12 August 2026

With the market turning bullish we will be going in on a fair launch on the 20th of April. Development has been in top gear and we will be sharing updates on progress made with the community Marketing activities will also kick start. We appreciate everyone for their patience. Let's make it big fellas!!!

18 Jan 2022, 17:47 UTC492 viewsread 12 August 2026
Photo

Decenta Yield will be launching on fantom Blockchain due to the ongoing hype around Fantom Get ready ⚡⚡⚡

16 Jan 2022, 14:41 UTC582 viewsread 12 August 2026

✅ • Our presale will hold @Idoscan1 ✅ • Presale Date and details will be communicated. https://twitter.com/De_Yield/status/1482719330454446089?t=aPudxDZjeJ5XBia2-jeHEA&s=09

11 Jan 2022, 14:30 UTC488 viewsread 12 August 2026

Decenta Yield The first 5 in 1 aggregator yield on the blockchain. Decenta services; -Decenta pad -Decenta Dao -Decenta Aggregator -Decenta Dex -Decenta Bridge Links TG channel: T.me/dyield TG chat: T.me/dyieldchat Twitter Community https://Twitter.com/De_yield Website: https://decentayield.com/

Showing the 5 most recent of 5 posts we hold for @Dyield. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

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.

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

“Decenta Yield” (@Dyield), 15 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/Dyield.

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.