Telegram RegisterThe public register of Telegram
Telegram profile photo for WS云控 WS双向云控 LINE云控 TG双向云控 全球IP

Channel

WS云控 WS双向云控 LINE云控 TG双向云控 全球IP

@WhatsAppHashChannelK

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

2,838subscribers

+118 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002068991379
TypeChannel
Username@WhatsAppHashChannelK
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/WhatsAppHashChannelK

Growth

2,7002,8962,7987 August 2026 — 2,720 subscribers7 August 2026 — 2,721 subscribers11 August 2026 — 2,703 subscribers14 August 2026 — 2,716 subscribers17 August 2026 — 2,700 subscribers20 August 2026 — 2,778 subscribers24 August 2026 — 2,845 subscribers27 August 2026 — 2,843 subscribers29 August 2026 — 2,896 subscribers1 September 2026 — 2,850 subscribers5 September 2026 — 2,834 subscribers10 September 2026 — 2,838 subscribers2,8387 August 202610 September 2026
12 measurements spanning 34 days, net +118. 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 2,671–2,925 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 07:582,838+4
5 Sept 2026, 11:222,834-16
1 Sept 2026, 20:042,850-46
29 Aug 2026, 19:382,896+53
27 Aug 2026, 05:342,843-2
24 Aug 2026, 05:432,845+67
20 Aug 2026, 09:562,778+78
17 Aug 2026, 12:562,700-16
14 Aug 2026, 08:272,716+13
11 Aug 2026, 03:112,703-18
7 Aug 2026, 17:012,721+1
7 Aug 2026, 16:322,720first reading

Engagement

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

Reaction mix

11 reactions across 4 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11100.0%

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

Measured over the 14 most recent posts we hold, published 15 June 2026 to 6 August 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

6 Aug 2026, 09:30 UTC219 viewsread 7 August 2026
Photo

📱个号升级真人号版本 1.在管理老号的基础上模拟真人化操作 2.稳上加稳,更加耐用 【投放专用】 用于广告投放,可进行管理fb广告资产(管理账户/主页/bm) @MOCOKK

6 Aug 2026, 08:00 UTC241 viewsread 7 August 2026

WS双向群发,美国有量 美国号发送 👩🏻‍💻@MOCOKK

4 Aug 2026, 12:41 UTC318 viewsread 7 August 2026

FB出三月混合老号,真人号 模拟真人养号,用于管理,群发 👩🏻‍💻@MOCOKK

1 Aug 2026, 11:48 UTC551 viewsread 7 August 2026

LINE双向群发,泰国,韩国本国号发送 台湾可接 LINE号出: 台湾 韩国 日本 泰国 👩🏻‍💻@MOCOKK

29 Jul 2026, 05:10 UTC759 views2 reactionsread 7 August 2026
Photo

星河 未来更新 工单链接直接点复制,不需要等网页跳转 @MOCOKK

2

21 Jul 2026, 13:22 UTC≈1,700 views3 reactionsread 7 August 2026
Photo

TG双向群发打粉,全球可接 巴西美国英国土耳其意大利荷兰墨西哥印度等本国号发送,没有本国号以欧美混号优先群发,均是包号包控,无视封控!精聊,兼职,股票,维权,资金盘,空降,电商均可接! TG双向群发,印度冰点价 LINE泰国,韩国,台湾双向群发,泰国,韩国本国号发送 WS双向群发除港澳台外,全球可接 😀@MOCOKK

3

16 Jul 2026, 08:46 UTC886 viewsread 7 August 2026
Photo

星河 未来 混合官方自养老号可上量 👩🏻‍💻@MOCOKK

7 Jul 2026, 14:04 UTC≈1,490 views0 reactionsread 7 August 2026

Tg双向打粉 意大利 荷兰 美国 印度 墨西哥 英国 埃及 印尼 等等多个国家可接本国打本国 TG图文超链全球可接 👩🏻‍💻 @MOCOKK

7 Jul 2026, 04:44 UTC≈1,170 viewsread 7 August 2026

神舟 WS 私信群发, 除美国巴西外都可接,需要滴滴 👩🏻‍💻@MOCOKK

4 Jul 2026, 07:27 UTC≈1,310 views1 reactionsread 7 August 2026

TG韩国双向群发,接单 有意向客户可以联系 👩🏻‍💻@MOCOKK

1

19 Jun 2026, 07:15 UTC≈1,770 viewsread 7 August 2026

Ws神舟双向群发-除美国不接,欧洲,南美,亚洲,非洲,中东,稳定打 私信群发,带后台 👩🏻‍💻@MOCOKK

18 Jun 2026, 06:22 UTC≈1,600 views5 reactionsread 7 August 2026
Photo

LINE TW空降群发 懂的客户来 👩🏻‍💻@MOCOKK

5

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

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

“WS云控 WS双向云控 LINE云控 TG双向云控 全球IP” (@WhatsAppHashChannelK), 2,838 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/WhatsAppHashChannelK.

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.