Telegram RegisterThe public register of Telegram
Telegram profile photo for दिसावर के हेकर

Channel

दिसावर के हेकर

@vvfnjkhfgnnjj

On this record: Topic · Previous handles · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

45,453subscribers

-2,485 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002000322707
TypeChannel
Username@vvfnjkhfgnnjj
Description👑ɪᴍᴀɴᴅᴀʀɪ👑 ᴇᴋ ᴍᴀʜɴɢᴀ ꜱʜᴏᴋ ʜᴇ, ᴊɪꜱᴇ ᴋᴀʀɴᴀ ʜᴀʀ ᴋɪꜱɪ ᴋᴇ ʙᴀꜱ ᴋɪ ʙᴀᴛ ɴᴀʜɪ
CreatedBetween 1 November 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held20
On Telegramt.me/vvfnjkhfgnnjj

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 39% 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.

Previous handles

@vvfnjkhfgnnjj was previously reachable at these 15 handles, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@vxgjgjijggjig
held 11 November 2026 – 11 November 2026
@fufjjggjvjjv
held 25 October 2026 – 25 October 2026
@jxnxnnxnn
held 29 September 2026 – 29 September 2026
@gjfhhffhch
held 19 September 2026 – 19 September 2026
@djjxjxjdjdji
held 27 August 2026 – 27 August 2026
@hdjdjdkrjfj
held 27 August 2026 – 27 August 2026
@fkdjjdjdjxjdb
held 24 August 2026 – 24 August 2026
@bgtbbtbttb
held 23 August 2026 – 23 August 2026
@gufhfhjg
held 22 August 2026 – 22 August 2026
@gjjgjyjyy
held 21 August 2026 – 21 August 2026
@fffcdcdxxzxz
held 17 August 2026 – 17 August 2026
@bxndjdjdjjvdds
held 13 August 2026 – 13 August 2026
@udndjshdhj
held 10 August 2026 – 10 August 2026
@jdjdjdhdhhdhf
held 8 August 2026 – 8 August 2026
@hhhjshshdh
held 7 August 2026 – 7 August 2026

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 forms a group of 2 channels linked by matching posts. 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
@hejsjsudjxjxj/6986647 Aug 2026, 16:46 UTC@vvfnjkhfgnnjj/1294943 · this entry9 Aug 2026, 18:53 UTC1.002 days
@vvfnjkhfgnnjj/1289064 · this entry7 Aug 2026, 03:54 UTC@hejsjsudjxjxj/71090013 Aug 2026, 03:08 UTC1.006 days
@vvfnjkhfgnnjj/1307108 · this entry17 Aug 2026, 17:05 UTC@hejsjsudjxjxj/71670117 Aug 2026, 18:47 UTC1.001.7 hours
@hejsjsudjxjxj/72128320 Aug 2026, 04:58 UTC@vvfnjkhfgnnjj/1314088 · this entry21 Aug 2026, 13:28 UTC1.0033 hours
@vvfnjkhfgnnjj/1318096 · this entry23 Aug 2026, 13:30 UTC@hejsjsudjxjxj/72876623 Aug 2026, 16:49 UTC1.003.3 hours
@vvfnjkhfgnnjj/1370206 · this entry18 Sept 2026, 18:52 UTC@hejsjsudjxjxj/78201818 Sept 2026, 19:02 UTC1.0010 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
@hejsjsudjxjxj10 (8/8 hand-verifiable sample passed)1.0056 minutesthis entry (6–4)

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. 4 of the 4 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 37 comparable posts for this entry, running 7 August 2026 to 11 November 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 2 channels, the one whose matching posts we hold earliest is @vvfnjkhfgnnjj — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 17 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 2 registered channels linked by matching posts. 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.

Growth

45,45347,93846,695.57 August 2026 — 47,938 subscribers7 August 2026 — 47,938 subscribers8 August 2026 — 47,880 subscribers10 August 2026 — 47,849 subscribers10 August 2026 — 47,849 subscribers13 August 2026 — 47,680 subscribers17 August 2026 — 47,433 subscribers17 August 2026 — 47,433 subscribers21 August 2026 — 47,344 subscribers22 August 2026 — 47,382 subscribers23 August 2026 — 47,316 subscribers24 August 2026 — 47,328 subscribers27 August 2026 — 47,240 subscribers27 August 2026 — 47,257 subscribers19 September 2026 — 46,485 subscribers29 September 2026 — 46,348 subscribers25 October 2026 — 45,893 subscribers11 November 2026 — 45,731 subscribers11 November 2026 — 45,731 subscribers16 November 2026 — 45,453 subscribers7 August 202616 November 2026
20 measurements spanning 101 days, net -2,485. 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 45,080–48,311 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 05:5045,453-278
11 Nov 2026, 04:2245,731no change
11 Nov 2026, 03:4745,731-162
25 Oct 2026, 04:2245,893-455
29 Sept 2026, 16:4946,348-137
19 Sept 2026, 01:1946,485-772
27 Aug 2026, 17:3047,257+17
27 Aug 2026, 11:0947,240-88
24 Aug 2026, 04:1547,328+12
23 Aug 2026, 19:0147,316-66
22 Aug 2026, 07:4547,382+38
21 Aug 2026, 17:3047,344-89
17 Aug 2026, 18:0047,433no change
17 Aug 2026, 17:4547,433-247
13 Aug 2026, 14:1747,680-169
10 Aug 2026, 05:4547,849no change
10 Aug 2026, 05:3247,849-31
8 Aug 2026, 05:3247,880-58
7 Aug 2026, 13:5847,938no change
7 Aug 2026, 11:0347,938first reading

Engagement

266 posts held, back to 7 August 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 15 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.87%
avg views ÷ 45,453 subscribers
Avg views / post
1,300
37 posts measured
Reaction rate
0.255%
reactions ÷ views · ER floor
Posts in window
37
of 266 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. It is computed over the 25 of 37 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held266 (7 August 2026 – 11 November 2026)
Views total48,267
Reactions total105
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 04:22 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.

Reaction mix

1,020 reactions across 205 posts, in 13 distinct kinds. The most used accounts for 54.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤55154.0%
👍727.06%
🍓656.37%
💔565.49%
🕊525.10%
🆒504.90%
💘484.71%
🎉474.61%
🏆302.94%
🎄292.84%
💊151.47%
🖕30.294%
⚡20.196%

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 206 of the 266 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 1,020 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 266 most recent posts we hold, published 7 August 2026 to 11 November 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

Telegram’s own ‘edited’ marker: 1 of 37 posts held from the last 30 days (2.70%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 04:02 UTC86 viewsread 11 November 2026

मेंबरशिप बुकिंग चालू ⭐🥰🥰

11 Nov 2026, 04:02 UTC87 viewsread 11 November 2026

मेंबरशिप बुकिंग चालू है 𝗗𝗟 ✪ 𝗦𝗚 ✪ 𝗙𝗗 ✪ 𝗚𝗕 ✪ 𝗚𝗟 ✪ 𝗗𝗦 🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧 𝟭 जोड़ी 350 रुपए, 15 दिन 𝟭 जोड़ी 350 रुपए, 15 दिन 📩 गेम विद लोकेशन दी जाएगी 📩 मेंबरशिप के लिए नीली पट्टी पर क्लिक https://wa.me/918950269748 https://wa.me/918950269748 मेंबरशिप के लिए नीली पट्टी पर 🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧

10 Nov 2026, 17:03 UTC≈2,130 views2 reactionsread 11 November 2026
Sticker

Sticker, posted without a caption

❤2

10 Nov 2026, 17:03 UTC≈2,030 views2 reactionsread 11 November 2026
Voice message

Voice message, posted without a caption

❤2

10 Nov 2026, 17:03 UTC≈1,990 views3 reactionsread 11 November 2026

मेंबरशिप बुकिंग चालू है 𝗗𝗟 ✪ 𝗦𝗚 ✪ 𝗙𝗗 ✪ 𝗚𝗕 ✪ 𝗚𝗟 ✪ 𝗗𝗦 🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧 𝟭 जोड़ी 350 रुपए, 15 दिन 𝟭 जोड़ी 350 रुपए, 15 दिन 📩 गेम विद लोकेशन दी जाएगी 📩 मेंबरशिप के लिए नीली पट्टी पर क्लिक https://wa.me/918950269748 https://wa.me/918950269748 मेंबरशिप के लिए नीली पट्टी पर 🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧

❤3

10 Nov 2026, 17:03 UTC≈2,020 views1 reactionsread 11 November 2026

मेंबरशिप बुकिंग चालू ⭐🥰🥰

❤1

10 Nov 2026, 17:02 UTC≈1,830 views2 reactionsread 11 November 2026

मेंबरशिप बुकिंग चालू ⭐🥰🥰

❤2

10 Nov 2026, 16:48 UTC≈2,180 views13 reactionsread 11 November 2026

❤️ गाजियाबाद LEEK ❤️ 🤑 𝑺𝒊𝒏𝒈𝒍𝒆 0⃣5⃣ 𝙱𝙻𝙰𝚂𝚃🤑 🔥𝗦𝗶𝗻𝗴𝗮𝗹 𝗝𝗼𝗱𝗶 𝗕𝗹𝗮𝘀𝘁🔥 🌺🤑𝐁𝐢𝐠 𝐁𝐢𝐠 𝐂𝐨𝐧𝐠𝐭𝐚𝐭𝐮𝐥𝐢𝐭𝐢𝐨𝐧𝐬🤑🌺

❤4🍓2🎄1🎉1💊1💔1💘1🕊1

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

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

|| 𝐒𝐊 𝐒𝐀𝐓𝐓𝐀 𝐊𝐈𝐍𝐆 ||
@dyiidyid86d96e9 · 19,080
#1
🔰𝟭𝟬𝟭❥═❥𝗩𝗜𝗣 𝗛𝗔𝗥𝗨𝗣 🔰
@ufyfyfydyfyf · 23,646
#2
👉 बादशाह की हुकमत 🎁🎁
@xxxxooijhggy · 38,038
#3
बादशाह की नगरी
@sattaguruji494 · 38,450
#4
꧁गुरु सट्टा किंग꧂
@SABBIRKHANJI · 9,120
#5
𝙎𝘼𝙈𝙎𝙃𝘼𝙉 𝙆𝙄 𝙉𝘼𝙂𝙍𝙄
@samshansatta1 · 22,531
#6
꧁༒☬ साईं बाबा सट्टा किंग ☬༒꧂
@alfazvippu · 3,760
#7
꧁༒︎ ROBIN BHAI SATTA KING ༒︎ꨄ︎
@robinbhaisattaking123 · 8,627
#8
🔰𝗕𝗔𝗕𝗔 𝗦𝗔𝗧𝗧𝗔 𝗞𝗜𝗡𝗚 🔰
@wwwav0040 · 14,626
#9
गरीबों की किस्मत
@bdidjrdjdorjthxidjhrfhjzjd · 9,878 (as read 27 August 2026)
#10
Komal Satta Trick 2
@KOMALSATTATRICK2 · 19,483
#11
🦁ROCKY BHAI (R.B)🦁
@sgsjdkdjjdk · 18,412
#12
🅓︎🅚︎ ➤️ 🅑︎🅗︎🅐︎🅘︎
@jggyteght · 8,145 (as read 27 August 2026)
#13
ताज़ा खबर----➤️
@tajabah · 21,449
#14
🎖🎖 किस्मत का सट्टा 🎖🎖
@dbsbdbsnshrhs · 22,621
#15
महाकाली दरबार
@vjkvcycjxhgxc · 20,242
#16
महावीर
@hehejehehewu · 38,642 (as read 27 August 2026)
#17
shduhdhrhrirrjrrdddt
@shhsusisndjdjdoosns · 3
#18
♣️सट्टे का तहलका ®
@ffxxxxxxfffg · 24,189
#19
☞︎︎︎सिंगल का खिलाड़ी☜︎︎︎
@snsnnsnggg · 15,587 (as read 27 August 2026)
#20
🇵‌𝐚𝐭𝐡𝐚𝐧🇧‌𝐡𝐚𝐢
@pathanbhai_07 · 31,745
#21
🙏श्री बाबा वीरभद्र जी🙏
@sattababaka321 · 19,526
#22
𝘼𝙍𝙔𝘼𝙉 𝘽𝙃𝘼𝙄 𝙎𝘼𝙏𝙏𝘼 𝙆𝙄𝙉𝙂
@Aryanbhaiking560 · 19,119
#23
🌋सट्टे का बादशाह 🌋
@jbxdjkjddfk · 26,381
#24
🔰𝗦𝗔𝗧𝗧𝗔 𝗙𝗜𝗫𝗫𝗘𝗥 🔰💥
@sattafixsar2117 · 27,293 (as read 27 August 2026)
#25
सरकारी सट्टा चैनल
@gigxugfxu · 5,150
#26
🦁𝗦𝗔𝗧𝗧𝗔 𝗞𝗜𝗡𝗚🦁
@yuuitiufg · 18,118 (as read 27 August 2026)
#27
𓆉 🅻🅵🅶 🆂🆃🆃🅰 🅲🅾🅼🅿🅰🅽🆈
@yyfuf8y8y8y · 20,151 (as read 27 August 2026)
#28
🔱 𝐒𝐇𝐀𝐍𝐈𝐕𝐀𝐑 𝐒𝐀𝐓𝐓𝐀 🔱
@usnfkl · 22,533
#29
2 जोड़ी फिक्सर👍
@skskskc123 · 31,647 (as read 27 August 2026)
#30
सट्टे की जवानी
@kkjbvcvnnnjhgffhhhhggg · 22,383
#31
°°°°बाज भाई °°°°
@bazz_bhai01 · 22,221
#32
👑GAMER SATTA KING👑
@gcvhhbf · 2,849
#33
नाम तो सुना ही होगा
@sdsdsdsdsdsd11111 · 16,527
#34
🧚🧞‍♀ LUCKY BHAI 🧞‍♀🧚‍♀
@afh751 · 1,797
#35
🦋सिंगल जोड़ी किंग🦋
@hfhfgfcscgh · 17,872
#36
०० गेम चेंजर 786 ✌️
@sattaking9797 · 27,286 (as read 27 August 2026)
#37
GAUTAM BHAI KHAIWAL 🙏
@fdsdgfdxgfsxxvc · 7,295
#38
🆂🅰🆃🆃🅰 🅺🅸🅽🅶
@gkkgjgigurhh · 25,448
#39
𝗙𝗜𝗫𝗫𝗘𝗥 𝗞𝗜𝗡𝗚 ༆
@saxaxaxxaxaxaa · 1,898
#40
𝗥𝗢𝗖𝗞𝗬 𝗕𝗛𝗔𝗜 (𝗖𝗥𝗢𝗦𝗦𝗜𝗡𝗚)
@hhdfnvv · 2,483
#41
❣ 𝐒𝐀𝐓𝐓𝐀 𝐊𝐈𝐍𝐆 ❣
@dyhgdssiuhfdihf · 5,384
#42
फिक्स जोड़ी सट्टा ट्रिक
@sattadon_phh · 31,773
#43
AR SATTA TRICK™
@ARSATTATRICK · 51,138
#44
🐅रिजल्ट फास्ट ग्रुप🐅
@shyambabakikripah · 10,960
#45
सट्टे का बादशाह
@uggbcx · 14,979
#46
🇸𝗔𝗧𝗧𝗘 𝗦𝗘 𝗣𝗬𝗔𝗥
@Satta_king_disawar_satta · 20,183 (as read 27 August 2026)
#47
रतन खतरी boss 💥
@jsjdkdkdkkkx · 1,999
#48
Komal Satta Trick 3
@Komalsattatrick3 · 13,817
#49
💥𝗔𝗕𝗛𝗜𝗦𝗛𝗘𝗞 𝗕𝗛𝗔𝗜 𝗦𝗔𝗧𝗧𝗔 𝗞𝗜𝗡𝗚 👑
@Abhishekbhaisattaking2367 · 15,253 (as read 27 August 2026)
#50
Komal Satta Trick 4
@Komalsattatrick4 · 15,843
#51
महाकाल सत्ता किंग 𝗟𝗢𝗘𝗩
@vxdhuiih · 6,315
#52
MAHAKAL SATTA ❤️( DESAWAR DISAWAR )
@DESAWAR_SATTA · 108,017
#53

Read from Telegram’s recommendation API, most recently 27 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

MAHAKAL SATTA ❤️( DESAWAR DISAWAR )
@DESAWAR_SATTA · 108,017
Telegram ranks this channel #18 of 63 here — alongside 62 others — read 27 August 2026
RAJAN BHAI ❤️ ( SATTA KING )
@Rajan_bhai_satta_desawar · 82,348
Telegram ranks this channel #47 of 60 here — alongside 59 others — read 27 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“दिसावर के हेकर” (@vvfnjkhfgnnjj), 45,453 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/vvfnjkhfgnnjj.

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.