Telegram RegisterThe public register of Telegram
Telegram profile photo for nuco.cloud - official channel

Channel

nuco.cloud - official channel

@officialnucocloud

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

740subscribers

-4 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001499037518
TypeChannel
Username@officialnucocloud
CreatedBetween 1 June 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/officialnucocloud

Growth

7407447426 August 2026 — 744 subscribers6 August 2026 — 744 subscribers14 August 2026 — 740 subscribers6 August 202614 August 2026
3 measurements spanning 7 days, net -4. 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 739–745 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 08:38740-4
6 Aug 2026, 23:46744no change
6 Aug 2026, 23:35744first reading

Engagement

20 posts held, back to 5 August 2024the 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 3 July 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

3 Jul 2025, 12:59 UTC276 viewsread 6 August 2026

🚀 Big news from the nuco.cloud team We’ve officially launched the nuco.cloud API! This means you can now book, cancel, and fully manage GPU servers directly from your own code — with full automation and crypto support. It’s a major step forward for developers and AI startups looking to scale infrastructure on their terms. 🧠 Try it out or share with your dev team: 📘 API Docs: https://app.nuco.cloud/index.php?m=nuco

Signed Tobias Adler - CEO of nuco.cloud

3 Jul 2025, 12:59 UTC263 viewsread 6 August 2026
Photo

Photo, posted without a caption

Signed Tobias Adler - CEO of nuco.cloud

20 Feb 2025, 13:11 UTC403 viewsread 6 August 2026

nuco.cloud’s 2025 Roadmap update is here! Big things are coming! We’re scaling, expanding, and innovating to bring next-gen decentralized computing, AI-driven blockchain solutions, and more utility for $NCDT. 💡 What’s ahead? ✅ nuco.cloud SKYNET v2 development & launch ✅ AI Layer-2 blockchain rollout ...and much more! 📲 Check out the full breakdown on X: https://x.com/nucocloud/status/1892559861025747170 📖 Blog po

Signed Tobias Adler - CEO of nuco.cloud

9 Jan 2025, 17:59 UTC427 viewsread 6 August 2026

🚀 nuco.cloud AMA is Live! We’ve just released the full AMA video where the team answers your most pressing questions and shares exciting updates for the year ahead! 🎥 Watch it here: https://x.com/nucocloud/status/1877410867039580234?s=46&t=FL9N0K6FIQ7DHbpp2svdvg 📢 Engage with the announcement on X and share your thoughts. Don’t miss the chance to catch up on everything from $NCDT staking pools to the upcoming Lay

Signed Tobias Adler - CEO of nuco.cloud

21 Nov 2024, 16:31 UTC510 viewsread 6 August 2026

📢 Exciting Update: New $NCDT Staking Program Launching January 2025! We’re thrilled to announce our updated staking program, offering incredible rewards for $NCDT holders while supporting the nuco.cloud ecosystem. Program Details: 🔒 3 months: 25% APY + Uniswap trading fees 🔒 6 months: 37.5% APY + Uniswap trading fees 🔒 12 months: 50% APY + Uniswap trading fees Program Start Date: Early January 2025. This is your

Signed Tobias Adler - CEO of nuco.cloud

21 Nov 2024, 16:31 UTC359 viewsread 6 August 2026
Photo

Photo, posted without a caption

Signed Tobias Adler - CEO of nuco.cloud

14 Nov 2024, 16:56 UTC519 viewsread 6 August 2026

‼️ Big News ‼️ In response to your requests for enhanced token utilities, we’re excited to announce the launch of our AI-focused Layer-2 blockchain in 2025! This new development brings a suite of impactful features for $NCDT holders, designed to expand value and strengthen our ecosystem. Here’s what to expect: - All transactions on our blockchain will be settled in $NCDT, reinforcing utility and value for token ho

Signed Tobias Adler - CEO of nuco.cloud

14 Nov 2024, 16:54 UTC305 viewsread 6 August 2026
Photo

Photo, posted without a caption

Signed Tobias Adler - CEO of nuco.cloud

7 Nov 2024, 14:21 UTCviews —

nuco.cloud - official channel pinned «Hello Nuconators, we are doing it again: Adding more Utility 💪🏻 We’re excited to introduce the Nuco.cloud Affiliates Program, offering a new earning opportunity for our community and adding another utility for $NCDT. Allowing participants to earn rewards…»

7 Nov 2024, 14:20 UTC752 viewsread 6 August 2026

Hello Nuconators, we are doing it again: Adding more Utility 💪🏻 We’re excited to introduce the Nuco.cloud Affiliates Program, offering a new earning opportunity for our community and adding another utility for $NCDT. Allowing participants to earn rewards for helping expand our PRO client base. Here’s what you need to know about: - Earn a continuous 5% of all revenue generated by the clients you refer to Nuco.clou

Signed Tobias Adler - CEO of nuco.cloud

7 Nov 2024, 14:20 UTC597 viewsread 6 August 2026
Photo

Photo, posted without a caption

Signed Tobias Adler - CEO of nuco.cloud

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

Citation-graph rank — 1,362,016 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.

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

“nuco.cloud - official channel” (@officialnucocloud), 740 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/officialnucocloud.

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.