Telegram RegisterThe public register of Telegram
Telegram profile photo for 墨染的大本营🍇

Channel

墨染的大本营🍇

@whatsapp6668888

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

23subscribers

-1 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-1001986250955
TypeChannel
Username@whatsapp6668888
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live16 November 2026
Measurements held5
Confirmed unchanged5 times, most recently 16 November 2026
On Telegramt.me/whatsapp6668888

Topic

Hacking & security — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 85% 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 the other topics.

Growth

2325247 August 2026 — 24 subscribers11 August 2026 — 24 subscribers13 September 2026 — 25 subscribers27 September 2026 — 24 subscribers15 October 2026 — 23 subscribers7 August 202615 October 2026
5 measurements spanning 69 days, net -1. 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 23–25 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Oct 2026, 01:0623-1
27 Sept 2026, 06:2224-1
13 Sept 2026, 11:0025+1
11 Aug 2026, 10:3224no change
7 Aug 2026, 12:0924first reading

Engagement

20 posts held, back to 7 April 2024 — 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 28 September 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2024, 13:11 UTC238 viewsread 11 August 2026

打粉劫持需提前预定,噶噶好用,手快有手慢无

23 Jul 2024, 00:27 UTC256 viewsread 11 August 2026

印尼,马来,新加坡支付通道有需要的来,支持大额

22 Jul 2024, 12:13 UTC247 viewsread 11 August 2026

出售美国商店id 可改绑自己手机号买一次可使用一辈子,任意下载外版应用

14 May 2024, 09:50 UTC228 viewsread 11 August 2026

各国老号,个人劫持,商业劫持现货,混合快打随时可安排

14 Apr 2024, 16:13 UTC238 viewsread 11 August 2026

印尼个人,混合老号,混合快打,个人劫持,现货

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

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

“墨染的大本营🍇” (@whatsapp6668888), 23 subscribers as measured 15 October 2026. Telegram Register, tgregister.com/channel/whatsapp6668888.

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.