Channel

此群解散，将不再维护，请进入新群！

@vjjkjub

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

1subscribers

+0 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	-1002046654930
Type	Channel
Username	@vjjkjub
Created	Between 1 November 2023 and 23 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	14 August 2026
Last confirmed live	15 September 2026
Measurements held	2
On Telegram	t.me/vjjkjub

Growth

2 measurements spanning 7 days. 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)	Subscribers	Change
14 Aug 2026, 16:31	1	no change
7 Aug 2026, 12:40	1	first reading

Engagement

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

What this channel posts

Links: 87

Lifetime counters from Telegram’s own channel header, read 14 August 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

3 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share	Share, drawn
❤	3	100.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 1 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 3 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 23 May 2024 to 23 May 2024, 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

23 May 2024, 06:43 UTC50 views3 reactionsread 14 August 2026

Forwarded from @fdsdgsdgds

👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网警监控,点击进安全群🔰 👁本群已被网…

❤3

23 May 2024, 06:06 UTC17 viewsread 14 August 2026

Forwarded from @fdsdgsdgds

23 May 2024, 06:00 UTC2 viewsread 14 August 2026

Forwarded from @fdsdgsdgds

23 May 2024, 06:00 UTC3 viewsread 14 August 2026

Forwarded from @fdsdgsdgds

23 May 2024, 05:58 UTC1 viewsread 14 August 2026

Forwarded from @fdsdgsdgds

23 May 2024, 05:57 UTC1 viewsread 14 August 2026

Forwarded from @fdsdgsdgds

23 May 2024, 05:38 UTC1 viewsread 14 August 2026

Forwarded from @fdsdgsdgds

23 May 2024, 05:36 UTC1 viewsread 14 August 2026

Forwarded from @fdsdgsdgds

23 May 2024, 05:20 UTC1 viewsread 14 August 2026

Forwarded from @fdsdgsdgds

23 May 2024, 04:48 UTC1 viewsread 14 August 2026

Forwarded from @fdsdgsdgds

23 May 2024, 04:45 UTC1 viewsread 14 August 2026

Forwarded from @fdsdgsdgds

23 May 2024, 04:43 UTC1 viewsread 14 August 2026

Forwarded from @fdsdgsdgds

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

此群不在维护，注意！注意！
@fdsdgsdgds · 320 posts

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

“此群解散，将不再维护，请进入新群！” (@vjjkjub), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/vjjkjub.

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.