Telegram RegisterThe public register of Telegram
Telegram profile photo for GDRAGON channel

Channel

GDRAGON channel

@GdragonVIP

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

1,465subscribers

+70 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001050702812
TypeChannel
Username@GdragonVIP
Created26 June 2016measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live25 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/GdragonVIP

Growth

1,3811,4651,4235 August 2026 — 1,395 subscribers6 August 2026 — 1,395 subscribers7 August 2026 — 1,394 subscribers9 August 2026 — 1,391 subscribers12 August 2026 — 1,390 subscribers16 August 2026 — 1,384 subscribers18 August 2026 — 1,382 subscribers22 August 2026 — 1,381 subscribers25 August 2026 — 1,465 subscribers5 August 202625 August 2026
9 measurements spanning 19 days, net +70. 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 1,368–1,478 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 10:261,465+84
22 Aug 2026, 08:171,381-1
18 Aug 2026, 23:271,382-2
16 Aug 2026, 03:031,384-6
12 Aug 2026, 12:441,390-1
9 Aug 2026, 21:581,391-3
7 Aug 2026, 00:321,394-1
6 Aug 2026, 07:501,395no change
5 Aug 2026, 23:441,395first reading

Engagement

7 posts held, back to 27 February 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 7 posts for this entry, the most recent from 2 March 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Mar 2025, 19:53 UTC≈7,900 views172 reactionsread 6 August 2026
File

File, posted without a caption

Signed Shaghayegh

2 Mar 2025, 19:52 UTC≈7,020 views73 reactionsread 6 August 2026
Photo

G-Dragon 3RD ALBUM 'UBERMENSCH' [250225] 🐉 @GdragonVIP 🐉 #UBERMENSCH

Signed Shaghayegh

27 Feb 2025, 18:31 UTC≈6,250 views48 reactionsread 6 August 2026
Photo

آپدیت اینستا ahnahr 😍 🐉 @GdragonVIP 🐉 #insta

Signed Shaghayegh

27 Feb 2025, 18:17 UTC≈5,700 views48 reactionsread 6 August 2026
Photo

آپدیت اینستا دارا😍 🐉 @GdragonVIP 🐉 #insta #Dara

Signed Shaghayegh

27 Feb 2025, 18:14 UTC≈4,400 views44 reactionsread 6 August 2026
Photo

آپدیت اینستا سی ال از پارتیشون مثل اینکه تولد سی ال هستش😍😍 ته یانگ، دارا، سون ، سوهیون ... 😍 🐉 @GdragonVIP 🐉 #insta #CL

Signed Shaghayegh

27 Feb 2025, 18:09 UTC≈3,880 views29 reactionsread 6 August 2026
Photo

تو اینستا داشتم پستای کیکو رو چک میکردم یهو دیدم جی دی پست اخرشو لایک کرده، کیکو رفته بوده بوسان😄😄😁😐 🐉 @GdragonVIP 🐉 #insta #kiko

Signed Shaghayegh

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

Citation-graph rank

Citation-graph rank — 1,537,786 of 1,602,868entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“GDRAGON channel” (@GdragonVIP), 1,465 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/GdragonVIP.

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.