Telegram RegisterThe public register of Telegram
Telegram profile photo for VIP Cloud Log

Channel

VIP Cloud Log

@vipcloudcc

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

181subscribers

+6 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003854626261
TypeChannel
Username@vipcloudcc
CreatedBetween 1 February 2026 and 24 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live1 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 1 October 2026
On Telegramt.me/vipcloudcc

Topic

Gambling & betting — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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

1751811788 August 2026 — 175 subscribers8 August 2026 — 175 subscribers23 August 2026 — 176 subscribers9 September 2026 — 177 subscribers16 September 2026 — 179 subscribers1 October 2026 — 181 subscribers8 August 20261 October 2026
6 measurements spanning 55 days, net +6. 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 174–182 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 15:21181+2
16 Sept 2026, 21:38179+2
9 Sept 2026, 18:17177+1
23 Aug 2026, 19:24176+1
8 Aug 2026, 14:02175no change
8 Aug 2026, 01:32175first reading

Engagement

20 posts held, back to 24 May 2026 — 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 20 posts for this entry, the most recent from 22 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

31 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 71.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁2271.0%
👍825.8%
👏13.23%

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

Measured over the 20 most recent posts we hold, published 24 May 2026 to 22 July 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.

Recent posts

22 Jul 2026, 04:34 UTC166 views4 reactionsread 8 August 2026

违规通报 主机名:HKG-VDS-1uormhp4 处置原因:接到投诉此服务器IP为博彩提供网络分发 处置方法:永久暂停服务

👍2😁2

21 Jul 2026, 16:42 UTC178 views3 reactionsread 8 August 2026

违规通报 主机名:LAX-VPS-wipa5i3g 处置原因:接到投诉此服务器IP为博彩提供网络分发 处置方法:永久暂停服务

😁2👍1

21 Jul 2026, 06:25 UTC196 views4 reactionsread 8 August 2026

违规通报 主机名:HKG-VDS-r5x7bjm5 处置原因:二次滥用带宽(日流量165G) 处置方法:永久暂停服务

😁3👍1

28 Jun 2026, 09:55 UTC377 views4 reactionsread 8 August 2026

违规通报 主机名:LAX-VDS-B-r0e42m7c 处置原因:违规搭建或使用代理行为,特征扫描:xray 处置方法:永久暂停服务

👍2😁2

28 Jun 2026, 09:48 UTC367 views1 reactionsread 8 August 2026

违规通报 主机名:HKG-VDS-1uormhp4 处置原因:滥用带宽(日流量137G) 处置方法:暂停服务1天

😁1

24 Jun 2026, 15:16 UTC446 views1 reactionsread 8 August 2026

违规通报 主机名:HKG-VDS-C-6l7urwhy 处置原因:滥用带宽(日流量119G) 处置方法:暂停服务1天

😁1

20 Jun 2026, 01:11 UTC493 views1 reactionsread 8 August 2026
Photo

违规通报 主机名:LAX-VDS-C-adybzz6y 处置原因:严重滥用带宽(日流量545G) 处置方法:暂停服务7天

😁1

19 Jun 2026, 07:59 UTC477 views6 reactionsread 8 August 2026

产品通报 主机名:HKG-VDS-A-fnkq2x9t 处置原因:无工单无理由对我们支付接口投诉 处置方法:永久封禁服务,不提供退款

😁6

17 Jun 2026, 05:48 UTC449 views0 reactionsread 8 August 2026

违规通报 主机名:HKG-VDS-A-qobclzq5 处置原因:违规搭建或使用代理行为,特征扫描:xray 处置方法:永久暂停服务

16 Jun 2026, 14:09 UTC410 views2 reactionsread 8 August 2026

违规通报 主机名:HKG-VDS-C-pnu23hwo 处置原因:滥用带宽(日流量123G) 处置方法:暂停服务1天

👍2

14 Jun 2026, 04:46 UTC489 views3 reactionsread 8 August 2026

违规通报 主机名:LAX-VDS-C-r1exqfcs 处置原因:滥用带宽(日流量160G) 处置方法:暂停服务1天

😁3

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

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

“VIP Cloud Log” (@vipcloudcc), 181 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/vipcloudcc.

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.