Telegram RegisterThe public register of Telegram
Telegram profile photo for Spear Leaks

Channel

Spear Leaks

@spearleaks

2 usernames

On this record: Growth · Engagement · Reactions · Advertising · Posts · Citations · Handles named that no longer answer · Cite this entry

1,472subscribers

-182 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-1003177586036
TypeChannel
Usernames@spearleaks @spearrleaks
CreatedBetween 1 September 2025 and 31 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 September 2026
Measurements held20
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/spearleaks

Growth

1,4401,6541,5477 August 2026 — 1,654 subscribers7 August 2026 — 1,654 subscribers10 August 2026 — 1,575 subscribers10 August 2026 — 1,562 subscribers13 August 2026 — 1,447 subscribers13 August 2026 — 1,445 subscribers16 August 2026 — 1,444 subscribers17 August 2026 — 1,443 subscribers20 August 2026 — 1,441 subscribers20 August 2026 — 1,441 subscribers23 August 2026 — 1,442 subscribers23 August 2026 — 1,440 subscribers25 August 2026 — 1,441 subscribers29 August 2026 — 1,443 subscribers31 August 2026 — 1,448 subscribers1 September 2026 — 1,447 subscribers4 September 2026 — 1,455 subscribers4 September 2026 — 1,454 subscribers9 September 2026 — 1,470 subscribers9 September 2026 — 1,472 subscribers1,4727 August 20269 September 2026
20 measurements spanning 33 days, net -182. 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,408–1,686 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 23:161,472+2
9 Sept 2026, 12:421,470+16
4 Sept 2026, 20:381,454-1
4 Sept 2026, 11:391,455+8
1 Sept 2026, 00:481,447-1
31 Aug 2026, 14:471,448+5
29 Aug 2026, 06:251,443+2
25 Aug 2026, 18:531,441+1
23 Aug 2026, 15:521,440-2
23 Aug 2026, 01:261,442+1
20 Aug 2026, 07:431,441no change
20 Aug 2026, 00:221,441-2
17 Aug 2026, 11:121,443-1
16 Aug 2026, 21:581,444-1
13 Aug 2026, 12:281,445-2
13 Aug 2026, 10:261,447-115
10 Aug 2026, 17:561,562-13
10 Aug 2026, 13:071,575-79
7 Aug 2026, 21:031,654no change
7 Aug 2026, 17:171,654first reading

Engagement

20 posts held, back to 26 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 30 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

44 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3375.0%
🔥511.4%
🤝49.09%
😁12.27%
🤪12.27%

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 16 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 44 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 26 January 2026 to 30 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.

Advertising

Ad load
5.00%
1 of 20 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
1,070
over 1 measured post
Median views · rest
4,190
over 19 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 20 most recent posts we hold, published 26 January 2026 to 30 July 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

30 Jul 2026, 04:25 UTC472 views0 reactionsread 7 August 2026
Photo

🎉 $50 XMR Giveaway 🎉 Hosted By: @SpearProgramSupport Requirements: • Must be a member of @SpearCXMarket Entries: 1 Giveaway Ends In: 6 days, 23 hours and 59 minutes To participate in the giveaway, press the button below!

27 Jul 2026, 21:09 UTC≈2,410 viewsread 7 August 2026

Crypto.com VM (Upgraded users only) Leaked by @thxxxxxxxxxxxxxxxxx Note: We do not give support for free tools. Do not message us about updates. Leaks are not verified, or made by us. Use with caution. ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ ⚔️ Main Channel | Leaks | Chat | Forum | RDP

26 Jul 2026, 02:05 UTC738 viewsread 7 August 2026

Submit a leak for a FREE one week ad Spear has once again begun giving free one week ads for leaks. Message @SpearProgramSupport to submit a leak.

20 Jul 2026, 21:36 UTC≈1,070 views2 reactionsread 7 August 2026

Nexus Panel Rebrandable (Upgraded users only) Note: We do not give support for free tools. Do not message us about updates. Leaks are not verified, or made by us. Use with caution. ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ ⚔️ Main Channel | Leaks | Chat | Verified | Forum | RDP

2

20 Jul 2026, 21:35 UTC969 views1 reactionsread 7 August 2026

@Function Prompter (Upgraded users only) Note: We do not give support for free tools. Do not message us about updates. Leaks are not verified, or made by us. Use with caution. ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ ⚔️ Main Channel | Leaks | Chat | Verified | Forum | RDP

🤪1

16 Jul 2026, 01:36 UTC≈1,070 views4 reactionsread 7 August 2026
AdvertisementPhoto

👄@AddictionGateway AIO Panel A complete AIO panel built for stability and security, domain linking is controlled by us not using cloudflare APIs no more domain bans. Features -Real-time victim control -Live page steering -Live Screen Viewer Watch your targs live -Live Keylogger -Over 8 1:1 Crypto Exchanges -Multiple Hardware Wallet Pages -FA mailer with over 8 Templates and custom option -Token Harvesting for Gmail

4

25 Jun 2026, 17:28 UTC≈3,660 views0 reactionsread 7 August 2026

XMR.gg Exploit Note: We do not give support for free tools. Do not message us about updates. Leaks are not verified, or made by us. Use with caution. ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ ⚔️ Main Channel | Leaks | Chat | Verified | Forum | RDP

17 Jun 2026, 21:49 UTC≈4,260 viewsread 7 August 2026

@Fuction Nexus Panel Note: We do not give support for free tools. Do not message us about updates. Leaks are not verified, or made by us. Use with caution. ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ ⚔️ Main Channel | Leaks | Chat | Verified | Forum | RDP

17 Jun 2026, 21:43 UTC≈2,240 views1 reactionsread 7 August 2026

Gate.io VM Leaked by @antibotdevlopment Note: We do not give support for free tools. Do not message us about updates. Leaks are not verified, or made by us. Use with caution. ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ ⚔️ Main Channel | Leaks | Chat | Verified | Forum | RDP

1

2 Jun 2026, 20:50 UTC≈3,890 views1 reactionsread 7 August 2026

Casa.io VM Note: We do not give support for free tools. Do not message us about updates. Leaks are not verified, or made by us. Use with caution. ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ ⚔️ Main Channel | Leaks | Chat | Verified | Forum | RDP

🔥1

13 Apr 2026, 00:58 UTC≈5,340 views6 reactionsread 7 August 2026

Google Voice Autodialer Note: We do not give support for free tools. Do not message us about updates. Leaks are not verified, or made by us. Use with caution. ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ ⚔️ Main Channel | Leaks | Chat | Verified | Forum

6

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

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

“Spear Leaks” (@spearleaks), 1,472 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/spearleaks.

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.