Telegram RegisterThe public register of Telegram
Telegram profile photo for uNode.net

Channel

uNode.net

@uNodeHosting

On this record: Growth · Engagement · Posts · Citations · Cite this entry

56subscribers

+2 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-1003957840906
TypeChannel
Username@uNodeHosting
CreatedBetween 1 April 2026 and 28 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live2 September 2026
Measurements held4
Confirmed unchanged3 times, most recently 2 September 2026
On Telegramt.me/uNodeHosting

Growth

5456557 August 2026 — 54 subscribers10 August 2026 — 54 subscribers13 August 2026 — 55 subscribers20 August 2026 — 56 subscribers7 August 202620 August 2026
4 measurements spanning 13 days, net +2. 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 54–56 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Aug 2026, 05:0456+1
13 Aug 2026, 11:2855+1
10 Aug 2026, 08:4654no change
7 Aug 2026, 01:4654first reading

Engagement

6 posts held, back to 28 April 2026the 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 6 posts for this entry, the most recent from 30 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Jun 2026, 02:30 UTC≈4,970 viewsread 10 August 2026
Photo

Introducing: uNode V2 🚀 The cheapest prices for VPS hosting anywhere. Rent a UHQ VPS with any crypto, starting at only $0.0088! Commit to a billing cycle & save up to 32%. Sign up w/ Telegram @ uNode.net. No account or KYC required.

19 May 2026, 23:43 UTC≈1,790 viewsread 10 August 2026

🇳🇱 Amsterdam, NL location added, + restocked Buy VPS/RDP with crypto instantly with uNode. Dirt cheap, but high quality. No BS, just hosting. t.me/uNodeHosting

30 Apr 2026, 20:16 UTC234 viewsread 10 August 2026

Over the next week(s), uNode is expanding it's infrastructure and scaling capabilities, adding new datacenters, and rebuilding the dashboard. Many new features are on the way. Thanks for using uNode :)

29 Apr 2026, 20:27 UTC198 viewsread 10 August 2026
Photo

Welcome to uNode.net Updates 🔄 Anonymous cloud servers in one click. ☁️ Here we'll post about new features, restocks, new locations, and other improvements. Zero KYC. Excellent Prices. 90+ Cryptos Accepted. ⚡️ 60-Second Deploy - pick OS, click deploy, get root password and IP instantly 🔒 Zero KYC - sign up with Telegram, nothing else atm 🖥 10 Plans - 1 to 16 vCPU, 3 to 64 GB RAM, NVMe storage 🌐 Full Root + rDNS Ac

Showing the 6 most recent of 6 posts we hold for @uNodeHosting. 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 2 registered channels — 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 20 August 2026 — this entry's latest reading, not the date you are reading this.

“uNode.net” (@uNodeHosting), 56 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/uNodeHosting.

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.