Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗖𝗹𝗼𝘂𝗱 𝗦𝗵𝗼𝗽𝗶𝗲 </>

Channel

𝗖𝗹𝗼𝘂𝗱 𝗦𝗵𝗼𝗽𝗶𝗲 </>

@cloudshopie

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

167subscribers

-3 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002075183918
TypeChannel
Username@cloudshopie
Created2 November 2023 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live3 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/cloudshopie

Topic

Ecommerce storefront — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

167170168.511 August 2026 — 170 subscribers11 August 2026 — 170 subscribers19 September 2026 — 169 subscribers3 October 2026 — 167 subscribers11 August 20263 October 2026
4 measurements spanning 53 days, net -3. 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 167–170 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 18:59167-2
19 Sept 2026, 00:58169-1
11 Aug 2026, 10:12170no change
11 Aug 2026, 08:17170first reading

Engagement

18 posts held, back to 2 November 2023 — 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 18 posts for this entry, the most recent from 17 December 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

18 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍950.0%
🔥844.4%
❤15.56%

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

Measured over the 18 most recent posts we hold, published 2 November 2023 to 17 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

17 Dec 2025, 02:31 UTC≈2,050 viewsread 11 August 2026

👩‍💻 RDP / VPS IN STOCK 👩‍💻 ⚡️ vCPU: 2 vCPU - 4 vCPU ⚡️ RAM: 4GB - 8GB - 16GB ⚡️ Storage: 30GB - 125GB SSD ⚡️ Speed: Up to 2Gbps ❓ OS SUPPORTED (ALL OS): ☄️ Windows Server (All Versions) ☄️ Linux (Ubuntu, Debian, CentOS, Alma, Rocky, etc.) 👩‍💻 Access: Full Admin / Root 🌐 Location: Multiple Regions ⚡️ Highend Custom Solutions Also Available 🛡 Warranty: 25 Days ‼️ T&C Applies - Read Carefully 💭 DM to Buy: @Pirate

14 Dec 2025, 17:06 UTC651 views0 reactionsread 11 August 2026
Photo

👩‍💻 Linux VPS In Stock ⚡️ 4 vCPU (AMD EPYC) ⚡️ 32 GB RAM ⚡️ ~500 GB SSD Storage ⚡️ Ubuntu 24.04.3 LTS ⚡️ High-Speed Network ⚡️ Uptime Ready / Production Use ⚡️ Warranty – 1 Month ⚡️ Renewable Monthly 💭 Dm @Piratexd to Buy ‼️ T&C Applied – Read Carefully

7 Dec 2024, 13:37 UTC609 viewsread 11 August 2026
Photo

📣RDP In Stock ⚡️4vCPU ⚡️8GB RAM ⚡️200 Mbps Speed ⚡️Warranty - 1 Month 💭 Dm @Piratexd to Buy ‼️ T&C Applied – Read Carefully

22 Oct 2024, 09:48 UTC≈1,560 views1 reactionsread 11 August 2026
Photo

🔟 VPS Back In Stock ⚡️2vCPU ⚡️4GB RAM ⚡️100GB NVME ⚡️1Gbps Speed ⚡️Warranty - 20 Days ⚡️3vCPU ⚡️8GB RAM ⚡️200GB NVME ⚡️1Gbps Speed ⚡️Warranty - 20 Days ⚡️4vCPU ⚡️12GB RAM ⚡️250GB NVME ⚡️1Gbps Speed ⚡️Warranty - 20 Days ⚡️5vCPU ⚡️16GB RAM ⚡️300GB NVME ⚡️1Gbps Speed ⚡️Warranty - 20 Days 🎚️ AMD Ryzen 9 5950X CPU 🎚️ Need Custom Solution, Also Ping Me 💭 Dm @Piratexd to Buy ‼️ T&C Applied – Read Carefully

👍1

7 Mar 2024, 15:01 UTC≈3,230 views1 reactionsread 11 August 2026
Photo

🔟 RDPs Back In Stock ⚡️2vCPU ⚡️4GB RAM ⚡️100GB NVME ⚡️1Gbps Speed ⚡️Warranty - 20 Days ⚡️3vCPU ⚡️8GB RAM ⚡️200GB NVME ⚡️1Gbps Speed ⚡️Warranty - 20 Days ⚡️4vCPU ⚡️12GB RAM ⚡️250GB NVME ⚡️1Gbps Speed ⚡️Warranty - 20 Days ⚡️5vCPU ⚡️16GB RAM ⚡️300GB NVME ⚡️1Gbps Speed ⚡️Warranty - 20 Days 🎚️ AMD Ryzen 9 5950X CPU 🎚️ Need Custom Solution, Also Ping Me 💭 Dm @Piratexd to Buy ‼️ T&C Applied – Read Carefully

👍1

24 Dec 2023, 21:30 UTC≈3,010 views0 reactionsread 11 August 2026
Photo

⚠️⚠️⚠️⚠️ Dear Valued Clients, We're updating our pricing to enhance our services. Your satisfaction is crucial, and these changes will ensure continued quality. Thank you for your trust and understanding. Best Regards, Cloud Shopie

24 Dec 2023, 21:30 UTC≈2,740 views1 reactionsread 11 August 2026
Photo

⚠️⚠️⚠️⚠️ Dear Valued Client, Kindly be reminded to review and adhere to our Terms and Conditions for utilizing our cloud services. These guidelines ensure a secure and efficient collaboration. Your compliance is appreciated for a seamless experience. Best Regards, Cloud Shopie

👍1

6 Dec 2023, 20:37 UTC≈2,460 views0 reactionsread 11 August 2026
Photo

📣RDP In Stock ⚡️16vCPU ⚡️64GB RAM ⚡️1000 Mbps Speed ⚡️Warranty - 20 Days 💭 Dm @G4rxd to Buy ‼️ T&C Applied – Read Carefully

24 Nov 2023, 08:53 UTC≈1,740 views0 reactionsread 11 August 2026

☁️VPS In Stock ⚡1vCPU ⚡2GB RAM ⚡25GB SSD ⚡100 Mbps Speed ⚡Warranty - 25 Days 🎲Price Fixed :- @110₹ 💭 Dm @G4rxd to Buy ‼️ T&C Applied – Read Carefully

24 Nov 2023, 04:40 UTC≈2,050 viewsread 11 August 2026
Photo

📣VPS In Stock ⚡️2vCPU ⚡️4GB RAM ⚡️30GB SSD ⚡️1000 Mbps Speed ⚡️Warranty - 20 Days ⚡️2vCPU ⚡️8GB RAM ⚡️30GB SSD ⚡️1000 Mbps Speed ⚡️Warranty - 20 Days ⚡️4vCPU ⚡️16GB RAM ⚡️30GB SSD ⚡️1000 Mbps Speed ⚡️Warranty - 20 Days 🔟 RDP In Stock ⚡️2vCPU ⚡️8GB RAM ⚡️125GB SSD ⚡️1Gbps Speed ⚡️Warranty - 20 Days ⚡️2vCPU ⚡️16GB RAM ⚡️125GB SSD ⚡️2Gbps Speed ⚡️Warranty - 20 Days 🎚️ Need Custom Solution, Also Ping Me 💭 Dm @G4r…

12 Nov 2023, 16:52 UTC≈2,570 views1 reactionsread 11 August 2026

🔟 RDP In Stock ⚡️2vCPU ⚡️16GB RAM ⚡️125GB SSD ⚡️2Gbps Speed ⚡️Warranty - 20 Days 💭 Dm @G4rxd to Buy ‼️ T&C Applied – Read Carefully

👍1

12 Nov 2023, 06:33 UTC≈1,340 views1 reactionsread 11 August 2026

💥Diwali VPS Offer 💥 ⚡️4vCPU ⚡️8GB RAM ⚡️50GB SSD ⚡️500 Mbps Speed ⚡️Warranty - 20 Days ✅ @279₹ Only 💭 Dm @G4rxd to Buy ‼️ T&C Applied – Read Carefully

❤1

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

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.

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

“𝗖𝗹𝗼𝘂𝗱 𝗦𝗵𝗼𝗽𝗶𝗲 </>” (@cloudshopie), 167 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/cloudshopie.

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.