Telegram RegisterThe public register of Telegram

Channel

( 龙吸血鬼 ) • • ⓘ THE DRAGON VAMPIRE

@TDRAGONV

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

1,073subscribers

-1 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003810558666
TypeChannel
Username@TDRAGONV
CreatedBetween 1 February 2026 and 30 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/TDRAGONV

Growth

1,0731,0741,073.512 Aug 2026, 00:32 — 1,074 subscribers12 Aug 2026, 08:23 — 1,073 subscribers12 Aug 2026, 00:3212 Aug 2026, 08:23
2 measurements taken within a single day, 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 1,073–1,074 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 08:231,073-1
12 Aug 2026, 00:321,074first reading

Engagement

18 posts held, back to 30 April 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.40%
avg views ÷ 1,073 subscribers
Avg views / post
68.6
8 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
8
of 18 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held18 (30 April 20269 August 2026)
Views total549
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 00:32 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
3s
Average length
3s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

33 reactions across 4 posts, in 8 distinct kinds. The most used accounts for 15.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5168198692045325150515.2%
custom 5168222769631986275515.2%
custom 6273764651750658803515.2%
custom 6296099606971289112515.2%
custom 6298359764791332311515.2%
custom 516806978719187065539.09%
custom 625341810747428876439.09%
custom 516819027820439197326.06%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

Measured over the 18 most recent posts we hold, published 30 April 2026 to 9 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

9 Aug 2026, 22:49 UTC26 viewsread 12 August 2026
Forwarded from @JUHOTZ

HELP FORWARD! Hotz! We’re gathering ALL CORTIS ROLEPLAYERS for an exciting celebration of CORTIS' 1ST ANNIVERSARY on 18th August 2026. To participate, simply provide your full name, and your username. Send the details directly to @JuhotzzBot. Submission Format For Pers: Hi! I’m [Your Full Name], [Your Username] and im using [Your Muse]. Count me in for the fellowship! Thank you and have an amazing day! Submission F

9 Aug 2026, 22:48 UTC24 viewsread 12 August 2026
Forwarded from @youngjaeistPhoto

ㅤㅤ ㅤㅤㅤㅤㅤㅤ𝗪𝗛𝗔𝗧 𝗧𝗜𝗠𝗘 𝗜𝗦 𝗜𝗧? ㅤㅤㅤA little bit of this, a little bit of that— ㅤ somewhere along the way, 𝘴𝘦𝘷𝘦𝘯 𝘴𝘵𝘰𝘳𝘪𝘦𝘴 ㅤ𝘧𝘰𝘶𝘯𝘥 𝘵𝘩𝘦𝘮𝘴𝘦𝘭𝘷𝘦𝘴 running on the same clock. ㅤ Different hours, different characters, ㅤ ㅤone cycle waiting to be completed. ㅤㅤㅤ ㅤ𝙇𝙀𝙏’𝙎 𝙎𝙏𝘼𝙍𝙏 𝙒𝙄𝙏𝙃 𝙊𝙉𝙀. 🍉 ㅤㅤ

9 Aug 2026, 09:40 UTC34 viewsread 12 August 2026
Forwarded from @Hoonrift

‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎( 𝗛𝗘𝗟𝗣 𝗙𝗢𝗥𝗪𝗔𝗥𝗗 ) ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ CALLING OUR⁷ @HOONRIFT ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ AUDIENCE TO JOIN OUR ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ STREAM AS WE CELEBRATE ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎CORTIS’ FIRST ANNIVERSARY. ‎ ‎ ‎ ‎ ‎ ‎ SUBMIT YOUR NAME + @USERNAME + MUSE ‎ ‎ ‎ ‎ ‎ ‎ USING MONO thru @CORSRIFTbot ‎ ‎ ‎ ‎ ‎ ‎ And stay tuned for the stream. ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎

9 Aug 2026, 02:59 UTC28 viewsread 12 August 2026
Forwarded from @CHANTENNAPhoto

ㅤㅤ #01 AMPLIFY THE SIGNAL! 🎙✦ We are expanding the lineup and looking for sharp minds to take our broadcast worldwide. Care to tune in? ㅤㅤ

13 Jul 2026, 23:36 UTC429 viewsread 12 August 2026

NI HAO BOUND BOUND!!! Tebak siapa bangkit? Yap kami the dragon siap bangkit dan akan lapar SFS KEMBALI!!!!!👏🏻👏🏻👏🏻👏🏻👏🏻👏🏻👏🏻👏🏻👏🏻👏🏻 Jadi yok sfs yang banyak sama kita ges, kami laparrrrrrrr @TDRAGONVBOT

3 May 2026, 04:47 UTC616 views8 reactionsread 12 August 2026
Photo

𖤐 Shadow Update 🌟 a new trace appears in the night. JINGTIAN has just graced with a fresh post, revealing a fleeting yet captivating moment that lingers like a whisper in the dark. Every detail carries its own charm subtle, striking, and impossible to ignore. 🏮 假期快乐~☁️☀️ Do not let this pass unnoticed, follow the trace and witness it yourself. 🩸

custom 51681986920453251502custom 62737646517506588032custom 51681902782043919731custom 51682227696319862751custom 62534181074742887641custom 62983597647913323111

Showing the 12 most recent of 18 posts we hold for @TDRAGONV. 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,107,917 of 1,183,361entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 2 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.

Named by

Channels on the register whose posts name this channel's handle.

Names

Channels on the register whose handles appear in this channel's posts.

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

“( 龙吸血鬼 ) • • ⓘ THE DRAGON VAMPIRE” (@TDRAGONV), 1,073 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/TDRAGONV.

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.