Telegram RegisterThe public register of Telegram

Channel

Stark Network

@STARKxNETWORK0

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

902subscribers

+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-1002613778612
TypeChannel
Username@STARKxNETWORK0
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/STARKxNETWORK0

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 45% 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 why it has no browse page of its own yet.

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 word for word on 2 other registered channels. 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
@STARKxNETWORK0/269 · this entry12 May 2026, 06:45 UTC@StarkxOsint/6912 May 2026, 06:46 UTC1.00under a minute
@STARKxNETWORK0/270 · this entry12 May 2026, 07:26 UTC@StarkxOsint/7012 May 2026, 07:27 UTC1.00under a minute
@STARKxNETWORK0/288 · this entry22 May 2026, 08:14 UTC@StarkxOsint/7822 May 2026, 08:18 UTC1.004 minutes
@STARKxNETWORK0/290 · this entry14 Jun 2026, 05:31 UTC@StarkxOsint/9814 Jun 2026, 05:31 UTC1.00under a minute
@STARKxNETWORK0/291 · this entry24 Jun 2026, 04:01 UTC@StarkxOsint/12524 Jun 2026, 04:02 UTC1.00under a minute
@StarkxOsint/13429 Jun 2026, 03:43 UTC@STARKxNETWORK0/292 · this entry29 Jun 2026, 03:43 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@StarkxOsint7 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (52)
@StarkxNet6 (6/6 hand-verifiable sample passed)1.00under a minute@StarkxNet (42)

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 6 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 14 comparable posts for this entry, running 31 March 2026 to 17 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).

Across the whole group of 3, the earliest publisher we hold is @STARKxNETWORK0 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_source, last confirmed 8 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

9027 Aug 2026, 18:20 — 902 subscribers8 Aug 2026, 01:03 — 902 subscribers7 Aug 2026, 18:208 Aug 2026, 01:03
2 measurements taken within a single day. 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 901–903 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 01:03902no change
7 Aug 2026, 18:20902first reading

Engagement

20 posts held, back to 19 March 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
19.3%
avg views ÷ 902 subscribers
Avg views / post
174
1 post measured
Reaction rate
1.15%
reactions ÷ views · ER floor
Posts in window
1
of 20 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 17 July 2026
Posts held20 (19 March 202617 July 2026)
Views total174
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:03 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

Photos
1
Links
11

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

69 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 44.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3144.9%
❤‍🔥3043.5%
👨‍💻34.35%
👻34.35%
🗿11.45%
😢11.45%

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 11 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 69reactions 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 19 March 2026 to 17 July 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

17 Jul 2026, 14:02 UTC174 views2 reactionsread 8 August 2026

🔥 Dark Tunnel Config Available 🔥 ⚡ Fast & Stable Connection 📱 App: Dark Tunnel ✅Sim : Zio 4g/5g 🛡 Secure Tunnel Setup 🌐 Easy One-Click Connect ✅ Simple Setup ✅ Smooth Browsing Experience File Link : https://t.me/StarkKillDevbot?start=80d0d4a1  Regrading: @StarkxNetworkx 📥 Import Config → Tap Connect & Enjoy #Jio #HttpInjector #FreeNet #NonRecharge

2

6 Jul 2026, 15:20 UTCviews —

Stark Network pinned «🚀 𝐒𝐓𝐀𝐑𝐊 𝐍𝐄𝐓𝐖𝐎𝐑𝐊 🚀 All States Working ⚒ High Speed 🔥 Jio 4G/5G Users Dark Tunnel Config ❤️ 🔐 Dark Tunnel Lock Config 👉 : https://t.me/StarkKillDevbot?start=ea818e30 ⚡ High Speed • Stable • Easy Setup Join 𝐒𝐓𝐀𝐑𝐊 𝐍𝐄𝐓𝐖𝐎𝐑𝐊 for Daily Updates & New Configs!…»

6 Jul 2026, 15:20 UTC320 views2 reactionsread 8 August 2026

🚀 𝐒𝐓𝐀𝐑𝐊 𝐍𝐄𝐓𝐖𝐎𝐑𝐊 🚀 All States Working ⚒ High Speed 🔥 Jio 4G/5G Users Dark Tunnel Config ❤️ 🔐 Dark Tunnel Lock Config 👉 : https://t.me/StarkKillDevbot?start=ea818e30 ⚡ High Speed • Stable • Easy Setup Join 𝐒𝐓𝐀𝐑𝐊 𝐍𝐄𝐓𝐖𝐎𝐑𝐊 for Daily Updates & New Configs! 🚀

1👨‍💻1

29 Jun 2026, 03:43 UTC413 views1 reactionsread 8 August 2026
Photo

🚀 𝐒𝐓𝐀𝐑𝐊 𝐍𝐄𝐓𝐖𝐎𝐑𝐊 🚀 🔥 Jio 4G/5G Users 🔓 OpenSSH WS 👉 https://t.me/StarkKillDevbot?start=96ee4613 🔐 Dark Tunnel Lock Config 👉 https://t.me/StarkKillDevbot?start=b5f8b03b ⚡ High Speed • Stable • Easy Setup Join 𝐒𝐓𝐀𝐑𝐊 𝐍𝐄𝐓𝐖𝐎𝐑𝐊 for Daily Updates & New Configs! 🚀

1

24 Jun 2026, 04:01 UTC404 views0 reactionsread 8 August 2026

⚡ 𝐒𝐓𝐀𝐑𝐊 𝐇𝐎𝐒𝐓𝐈𝐍𝐆 ⚡ Host Your Telegram Bots! 🆓 Free Plan — 5 Bots 🔒 Secure & Private ⚡ Fast & Stable 🔄 Auto-Restart on Crash 📦 Auto Module Install 🛡️ 24/7 Uptime 👉 @StarkCloudHostBot 📢 @StarkXNetworkx | 💬 @Starkxkesari

14 Jun 2026, 05:31 UTC471 views1 reactionsread 8 August 2026

🔥 Dark Tunnel Config Available 🔥 ⚡ Fast & Stable Connection 📱 App: Dark Tunnel ✅Sim : Jio 4g/5g 🛡 Secure Tunnel Setup 🌐 Easy One-Click Connect ✅ Simple Setup ✅ Smooth Browsing Experience  Link : https://t.me/StarkKillDevbot?start=71b239b1 📥 Import Config → Tap Connect → Enjoy 🚀

1

22 May 2026, 08:14 UTC702 views2 reactionsread 8 August 2026

⚡ This Bot is actually free money. Upload any file on @StarkKillDevbot → You get a link → Share it anywhere → Every time someone opens it, you earn ₹0.5 That's it. No survey. No referral grind. Just a link doing the work for you. 💸 Withdraw to USDT or straight to your bank/UPI 🛡 Anti-fake system — only real visits count 🚀 Takes 30 seconds to start 👉 @StarkKillDevbot

2

21 May 2026, 13:15 UTC621 viewsread 8 August 2026

⚡ HTTP INJECTOR FILE ⚡ 📶 Jio 4G / 5G Non Recharge Working 🌍 Some States Working 🚀 High Speed & Stable Connection 🔒 Connect & Enjoy File : https://t.me/StarkKillDevbot?start=4a175143 #Jio #HttpInjector #FreeNet #NonRecharge

16 May 2026, 17:42 UTC771 views1 reactionsread 8 August 2026

⚡ HTTP INJECTOR FILE ⚡ 📶 Jio 4G / 5G Non Recharge Working 🌍 Some States Working 🚀 High Speed & Stable Connection 🔒 Connect & Enjoy File : https://t.me/StarkKillDevbot?start=9eb16948 #Jio #HttpInjector #FreeNet #NonRecharge

1

12 May 2026, 07:26 UTC764 viewsread 8 August 2026

🎮 FREE GAMING FILE 🎮 ⚡ Low Ping + Smooth Gaming ⚡ 🔥 Jio 4G / 5G Working 🚀 BGMI • FF • CODM Supported 🔗 Download Gaming File⁠� https://t.me/StarkKillDevbot?start=194f623c 💀 StarkKillDev�

12 May 2026, 06:45 UTC701 viewsread 8 August 2026

🌑 DARK TUNNEL FREE INTERNET FILE 🌑 ⚡ Jio 4G / 5G Unlimited Trick ⚡ 🔥 New Working Config Added 📶 Stable Speed + Smooth Browsing 🌍 All Area Supported 🚀 Easy To Connect ━━━━━━━━━━━━━━━ 🆕 NEW VPS FILE 🔗 Download VPS File⁠� 🌐 ALL AREA WORKING FILE 🔗 Download All Area File⁠� ━━━━━━━━━━━━━━━ ⚙ App Required : Dark Tunnel ✅ Import File & Tap Connect 🔥 Enjoy High Speed Internet 💀 Powered By StarkillDev �

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

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

“Stark Network” (@STARKxNETWORK0), 902 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/STARKxNETWORK0.

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.