Telegram RegisterThe public register of Telegram
Telegram profile photo for DARK X VPN

Channel

DARK X VPN

@darkxvpn2

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1,306subscribers

+1,072 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-1003896000016
TypeChannel
Username@darkxvpn2
CreatedBetween 1 February 2026 and 8 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 November 2026
Measurements held20
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/darkxvpn2

Topic

Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@darkxvpn2/28 · this entry10 Jun 2026, 07:06 UTC@Sync_connect/8910 Jun 2026, 07:09 UTC1.003 minutes
@darkxvpn2/44 · this entry19 Jul 2026, 14:02 UTC@Sync_connect/9619 Jul 2026, 14:05 UTC1.002 minutes
@darkxvpn2/45 · this entry20 Jul 2026, 14:40 UTC@Sync_connect/9720 Jul 2026, 14:41 UTC1.002 minutes
@darkxvpn2/46 · this entry21 Jul 2026, 00:06 UTC@Sync_connect/9821 Jul 2026, 00:06 UTC1.00under a minute
@darkxvpn2/47 · this entry22 Jul 2026, 13:39 UTC@Sync_connect/9922 Jul 2026, 13:44 UTC1.005 minutes
@darkxvpn2/48 · this entry25 Jul 2026, 12:55 UTC@Sync_connect/10125 Jul 2026, 12:58 UTC1.004 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@Sync_connect6 (6/6 hand-verifiable sample passed)1.002 minutesthis entry (6–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 10 comparable posts for this entry, running 8 June 2026 to 25 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @darkxvpn2 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with the channel listed below. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

1 more channel is in this same group but not listed individually here.

Growth

2341,3828087 August 2026 — 234 subscribers8 August 2026 — 234 subscribers8 August 2026 — 235 subscribers15 August 2026 — 239 subscribers23 August 2026 — 248 subscribers29 August 2026 — 254 subscribers8 September 2026 — 369 subscribers16 September 2026 — 577 subscribers29 September 2026 — 794 subscribers10 October 2026 — 1,197 subscribers14 October 2026 — 1,200 subscribers17 October 2026 — 1,211 subscribers20 October 2026 — 1,220 subscribers23 October 2026 — 1,234 subscribers26 October 2026 — 1,227 subscribers29 October 2026 — 1,234 subscribers1 November 2026 — 1,314 subscribers4 November 2026 — 1,382 subscribers8 November 2026 — 1,298 subscribers13 November 2026 — 1,306 subscribers1,3067 August 202613 November 2026
20 measurements spanning 97 days, net +1,072. 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 62–1,554 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 01:001,306+8
8 Nov 2026, 09:451,298-84
4 Nov 2026, 22:061,382+68
1 Nov 2026, 16:301,314+80
29 Oct 2026, 20:181,234+7
26 Oct 2026, 13:401,227-7
23 Oct 2026, 07:301,234+14
20 Oct 2026, 06:271,220+9
17 Oct 2026, 13:551,211+11
14 Oct 2026, 03:491,200+3
10 Oct 2026, 01:421,197+403
29 Sept 2026, 07:20794+217
16 Sept 2026, 01:40577+208
8 Sept 2026, 10:37369+115
29 Aug 2026, 11:45254+6
23 Aug 2026, 05:43248+9
15 Aug 2026, 06:03239+4
8 Aug 2026, 13:35235+1
8 Aug 2026, 10:03234no change
7 Aug 2026, 19:02234first reading

Engagement

20 posts held, back to 8 June 2026 — 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 40s
Average length
1m 40s

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

10 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤550.0%
👍220.0%
🔥220.0%
🥰110.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 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 10 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 8 June 2026 to 7 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

7 Aug 2026, 14:51 UTC40 viewsread 8 August 2026

📅 90 DAYS UNLIMITED WORKING FILES AVAILABLE 📂 🚫 NO LIMIT ♾️ 📉 NO DOWN 🛑 📥 COME IB - @lowky_on_fire 💬

7 Aug 2026, 14:51 UTC36 viewsread 8 August 2026

90 DAYS UNLIMITED WORKING FILES AVAILABLE NO LIMIT NO DOWN COME IB - @lowky_on_fire

25 Jul 2026, 12:55 UTC227 viewsread 8 August 2026

❤️Dialog Zoom Bypass V2ray📽️ Mobitel Zoom All Ip Hutch Zoom All Tiktok SLT ALL PACKAGES DIALOG ROUTER PACKAGES AIRTEL 260 Come Inbox To Buy 100GB Rs.200 Unlimited Rs.400 ✅Created By - ✨@lowky_on_fire🫥 👑 📥 Come Inbox To Buy v2rays 💵

22 Jul 2026, 13:39 UTC226 views4 reactionsread 8 August 2026

🖥️ LINODE PAID SERVER 🚀 🛠️ 2 DAYS WORK ⏳ ⚙️ All Configs LIMIT 4096 GB 💾 🈶 Dialog Speed Bypass Sometime Not Work Flight Mode On/Off ✈️ ❗️ AIRTEL FREEDOM ❗️ vless://[email protected]:443/?security=tls&encryption=none&headerType=none&type=tcp&flow=none&fp=chrome&sni=android.googleapis.com#Paid-Lowkey Free Server ❗️ AIRTEL 498 | 909 ❗️ vless://e60047ad-c93d-4ee6-917f-246e12552e72…

❤3🔥1

21 Jul 2026, 00:06 UTC229 viewsread 8 August 2026

📡 🈶 Dialog වල SpeedBypass කියයි අනම් මනම් කිව්වට සුට්ටක් Speed එකක් එනවනම් 4 Mbps වගේනම් මේක දෙගුනයකින් වගේ High Speed කරන Secret APN Setting ඇත 🚀. 🤝 Contact For Buy - @lowky_on_fire 👑 📲

20 Jul 2026, 14:40 UTC213 viewsread 8 August 2026

❤️Dialog Zoom Bypass V2ray📽️ Come Inbox To Buy 100GB Rs.200 Unlimited Rs.400 ✅Created By - ✨@lowky_on_fire🫥 👑 📥 Come Inbox To Buy v2rays 💵

19 Jul 2026, 14:02 UTC217 viewsread 8 August 2026

❤️Dialog Zoom Bypass V2ray📽️ vless://[email protected]:17490/?security=tls&encryption=none&headerType=none&type=tcp&flow=none&fp=chrome&sni=www.microsoft.com#PIS-Speed Bypass DALOG ZOOM ✅Created By - ✨@lowky_on_fire🫥 👑 📥 Come Inbox To Buy v2rays 💸 Speed Test නැත්තන් Off කරනව

15 Jul 2026, 16:48 UTC232 viewsread 8 August 2026

chat.whatsapp.com/HBZlJ0B8kdkGq3BGK09CQG 🛡️ 🆓 Free Editing Group WhatsApp 🈷️ 💎 Premium Edit 👑

11 Jul 2026, 04:09 UTC299 viewsread 8 August 2026

DZOOM trojan://[email protected]:443?security=tls&alpn=h2%2Chttp%2F1.1&headerType=none&fp=chrome&type=tcp&sni=aka.ms#xraylk-DZOOM A260YT trojan://[email protected]:443?security=tls&alpn=h2%2Chttp%2F1.1&headerType=none&fp=chrome&type=tcp&sni=upload.youtube.com#xraylk-A260YT SLTZOOM trojan://[email protected]:443?security=tls&alpn=h2%2Chttp%2F1.1&headerType=none&fp=chrome&type=tcp&sni=http%2F%2Fzoom.u…

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

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 6 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.

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

“DARK X VPN” (@darkxvpn2), 1,306 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/darkxvpn2.

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.