Telegram RegisterThe public register of Telegram
Telegram profile photo for BACKUP ®

Channel

BACKUP ®

@ultimateXcloudBACKUP

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

57,681subscribers

+51,763 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1003772462137
TypeChannel
Username@ultimateXcloudBACKUP
Descriptionhttps://t.me/ultimateXcloud ‌‌@ULPsearcherXRobot @AttA_mebot
Created8 February 2026 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live11 October 2026
Measurements held20
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/ultimateXcloudBACKUP

Topic

Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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

5,79896,54651,1727 August 2026 — 5,918 subscribers7 August 2026 — 5,918 subscribers8 August 2026 — 5,919 subscribers11 August 2026 — 5,898 subscribers14 August 2026 — 5,883 subscribers17 August 2026 — 5,859 subscribers20 August 2026 — 5,850 subscribers24 August 2026 — 5,832 subscribers27 August 2026 — 5,815 subscribers30 August 2026 — 5,800 subscribers2 September 2026 — 5,798 subscribers7 September 2026 — 96,546 subscribers10 September 2026 — 81,433 subscribers12 September 2026 — 76,921 subscribers14 September 2026 — 74,356 subscribers16 September 2026 — 74,530 subscribers18 September 2026 — 68,068 subscribers1 October 2026 — 58,336 subscribers6 October 2026 — 57,943 subscribers11 October 2026 — 57,681 subscribers57,6817 August 202611 October 2026
20 measurements spanning 64 days, net +51,763. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 04:1957,681-262
6 Oct 2026, 18:3657,943-393
1 Oct 2026, 16:1558,336-9,732
18 Sept 2026, 13:4168,068-6,462
16 Sept 2026, 02:5874,530+174
14 Sept 2026, 06:1874,356-2,565
12 Sept 2026, 14:4076,921-4,512
10 Sept 2026, 11:3981,433-15,113
7 Sept 2026, 05:3796,546+90,748
2 Sept 2026, 12:435,798-2
30 Aug 2026, 18:265,800-15
27 Aug 2026, 09:265,815-17
24 Aug 2026, 06:245,832-18
20 Aug 2026, 18:385,850-9
17 Aug 2026, 16:345,859-24
14 Aug 2026, 02:085,883-15
11 Aug 2026, 05:385,898-21
8 Aug 2026, 08:115,919+1
7 Aug 2026, 19:015,918no change
7 Aug 2026, 18:565,918first reading

Engagement

6 posts held, back to 8 February 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 78 pages 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 6 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
2

Lifetime counters from Telegram’s own channel header, read 12 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

423 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 52.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 536612598493428941822352.7%
custom 525812185109104377516839.7%
custom 5460648358169322543327.57%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 6 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 423 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 6 most recent posts we hold, published 8 February 2026 to 6 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
62
across the posts below
Posts paid on
4
of 4 we hold a reading for · 100%
Most on one post
27
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ultimateXcloudBACKUP. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 6 most recent posts we hold for this entry, published 8 February 2026 to 6 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

2 Sept 2026, 20:32 UTC≈122,000 views355 reactions27 Starsread 12 October 2026

Posted without readable text

custom 5366125984934289418213custom 5258121851091043775142

6 May 2026, 17:16 UTC≈46,700 views36 reactions13 Starsread 12 October 2026

linktr.ee/UltimateCloud linktr.ee/UltimateCloud linktr.ee/UltimateCloud

custom 546064835816932254326custom 536612598493428941810

2 Mar 2026, 23:47 UTC≈50,100 views32 reactions9 Starsread 12 October 2026

😎𝐓𝐞𝐥𝐞𝐠𝐫𝐚𝐦 𝐜𝐚𝐧 𝐛𝐚𝐧 𝐜𝐡𝐚𝐧𝐧𝐞𝐥/𝐛𝐨𝐭 𝐚𝐧𝐲𝐭𝐢𝐦𝐞, 𝐬𝐭𝐚𝐲 𝐡𝐞𝐫𝐞 𝐧𝐨𝐭 𝐭𝐨 𝐥𝐨𝐬𝐞 𝐮𝐬!! 🛡 🖥Web: ultimateulp.space

custom 525812185109104377526custom 54606483581693225436

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@ultimateXcloudBACKUP edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
7 September 2026
Most recent edit
7 September 2026

Forward network

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.

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

“BACKUP ®” (@ultimateXcloudBACKUP), 57,681 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/ultimateXcloudBACKUP.

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.