Telegram RegisterThe public register of Telegram

Channel

Durovs Cap Strategy

@DurovsCapStrategy

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

1,035subscribers

-10 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-1002934836881
TypeChannel
Username@DurovsCapStrategy
CreatedBetween 1 August 2025 and 14 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/DurovsCapStrategy

Growth

1,0351,0451,0407 August 2026 — 1,045 subscribers8 August 2026 — 1,045 subscribers10 August 2026 — 1,042 subscribers13 August 2026 — 1,035 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net -10. 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,034–1,047 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 09:151,035-7
10 Aug 2026, 13:261,042-3
8 Aug 2026, 00:191,045no change
7 Aug 2026, 12:331,045first reading

Engagement

20 posts held, back to 14 October 2025 — 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 pageof 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 21 January 2026. An engagement rate over an empty window would be a number about nothing.

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

561 reactions across 19 posts, in 29 distinct kinds. The most used accounts for 32.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤18432.8%
🔥14125.1%
👍549.63%
custom 5456264699798643395295.17%
custom 5456203011183371567244.28%
custom 5456305012361687632213.74%
👏142.50%
💯132.32%
🤯101.78%
custom 545614707782427411291.60%
🏆81.43%
💘71.25%
🥰61.07%
🍾50.891%
🫡50.891%
custom 545408367245605988640.713%
custom 545440725099717356230.535%
🐳30.535%
🤝30.535%
custom 545390726955927889020.357%
9 further kinds162.85%

Custom emoji. 7 of the rows above are 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 19 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 561reactions 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 14 October 2025 to 21 January 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

21 Jan 2026, 22:46 UTC606 views13 reactionsread 8 August 2026
Photo

Cap Strategy has sold it's 4th Durov's Cap. On January 18th, Cap #1454 was sold for 824 TON. This ton was used to buy over 6m CAPSTR (over 6% of the supply) and the tokens were promptly burned. Over 22% of CAPSTR has been burned since the start of this experiment, and there are 3 Caps currently listed for sale on our getgems account. We told you it wasn't dead! The strategy continues no matter what! Website | Gr…

🔥6👍3🤝3custom 54562030111833715671

18 Dec 2025, 16:06 UTC758 views14 reactionsread 8 August 2026
Photo

Is $CAPSTR dead? Absolutely not. Unlike other memecoins with no underlying mechanism, when there are periods like this with very little buying or selling, most people looking for a quick score have long sold, the project dies. But strategy tokens are different. The Cap Strategy getgems account still has our caps listed for sale. When those sell, there will be a buy and burn - and anyone holding $CAPSTR will benefit…

❤7custom 54562030111833715673👍2🔥2

26 Nov 2025, 17:16 UTC752 views23 reactionsread 8 August 2026
Photo

Cap Strategy has acquired Durov's Cap #1454 On 26 November 2025 at 17:06 UTC Big Moss | Coat of Arms | Aquamarine This is the 7th Cap acquired by the strategy. 3 Caps have sold, resulting in almost 12% of the supply burned. There are now 4 Caps for sale, viewable on the Cap Strategy Getgems account. TON and most of crypto is rekt, but $CAPSTR is still buying caps. 3789 TON is programming in to buy and burn $CAPSTR…

custom 545626469979864339510🔥5custom 54561470778242741124custom 54544072509971735623🤯1

14 Nov 2025, 15:13 UTC872 views10 reactionsread 8 August 2026
Photo

Hunting Durov's Cap #7 The flywheel continues. We have no Cabal support, total outsiders to the TON space. The team is a collection of Telegram Gift believers who have bought a lot of Durov's Caps and Plush Pepes. The strategy will continue to run. Slow, fast, or light speed. Fees will continue to acquire, and when we have enough to buy the floor, we'll buy it. When it sells, we'll buy and burn more $CAPSTR. Crypt…

🔥5⚡2❤2🤯1

11 Nov 2025, 14:10 UTC≈1,090 views13 reactionsread 8 August 2026
Photo

Cap Strategy has acquired it's 6th Durov's Cap. Cap #735 was purchased for 700 TON and relisted for 840 TON. You can see all the Caps for sale and full history on the Cap Strategy Getgems account. Less than 1 month since launch, the strategy has bought 6 Caps and sold 3, with 3 currently listed for sale. Almost 12% of $CAPSTR has been burned. Also today, the team has launched Pepe Strategy, which directly helps $C…

🔥4custom 54540836724560598864🍾2custom 54539072695592788902custom 54561470778242741121

10 Nov 2025, 17:06 UTC≈1,250 views19 reactionsread 8 August 2026
Photo

Now the Cap Strategy channel looks right 🎁 A few days ago, the team fees were used to purchase Durov's Cap #1950, and now the team has gifted the Cap to this channel. The Cap Strategy channel proudly displays it as a testament to the conviction of the team and the long term nature of the project. We have yet to get widespread exposure. We have yet to penetrate the TON cabal. But we will continue on making /progres…

🔥6custom 54562646997986433956custom 54561470778242741124🤣2custom 54540375960469067911

6 Nov 2025, 20:34 UTC≈1,720 views22 reactionsread 8 August 2026
Photo

This one is special. Cap Strategy has decided to use the team fees collected to purchase the first Durov's Cap the strategy acquired. This purchase by the team resulted in 1074 TON being used to buy over 5m $CAPSTR tokens and burn them. In total, almost 12% of $CAPSTR has been burned. Since launching less than 1 month ago, Cap Strategy has bought 5 Caps and sold 3. The flywheel continues to fly! Website | Group …

❤9🔥6🫡5custom 54540375960469067911custom 54541615015584306321

3 Nov 2025, 15:56 UTC≈1,420 views17 reactionsread 8 August 2026
Photo

Well that was fast! Cap Strategy has sold it's 2nd Durov's Cap. Cap #597 was held by the strategy for less than 16 hours before being sold. You can see the history on our Getgems profile. A total of 900 TON was used to buy over 4.4m $CAPSTR and promptly burn it. Over 6.6m tokens have now been burned in total. The deflationary flywheel spins on! Website | Group Chat | Trade

❤6🔥5👏3👀2custom 54539635594006608181

3 Nov 2025, 00:25 UTC≈1,540 views41 reactionsread 8 August 2026
Photo

Cap Strategy has acquired it's 5th Durov's Cap. Cap #597 was purchased for 750 TON and relisted for 900 TON. You can see all the Caps for sale and full history on the Cap Strategy Getgems account. The 5th acquisition shows that even with light trading volume, the strategy works. $CAPSTR now has 4 Caps for sale, over 4,000 TON in future buy and burns programmed in. Please tell your friends what we are doing, word …

🔥16❤14👍7🍾3custom 54562658465549107661

31 Oct 2025, 11:38 UTC≈1,350 views34 reactionsread 8 August 2026
Photo

Gm Cap Strategy Fam! Slowly, then all at once - that's the plan. The strategy has 3 Durov's Caps for sale, which means 3 seperate 1000+ TON buys are programmed in for the future. Even though trading has been slow the past week, the numbers don't lie, and the Caps will move up in price. The strategy is also inching closer to the next Cap purchase, and the flywheel will continue to spin. The team is going to give that…

🔥13👍11👏8custom 54541615015584306321custom 54562658465549107661

25 Oct 2025, 00:02 UTC≈4,220 views35 reactionsread 8 August 2026
Photo

Every day Cap Strategy is making /progress. Today the team reached out to DeDust and got the "Risky" label removed from the X1000 CAPSTR listing. $CAPSTR is now verified on Tonviewer and listed as a normal token on X1000. We have submitted all documents needed to whitelist the token on DeDust, we are thankful to the DeDust team for being approachable and having a conversation with us at this early stage of our proj…

❤35

23 Oct 2025, 15:47 UTC≈6,370 views100 reactionsread 8 August 2026
Video

This is Cap Strategy. 🎁 It's not a normal memecoin. $CAPSTR has a sustainable mechanism, inspired by Punk Strategy from ETH, but brought to TON and Telegram Gifts. $CAPSTR has 10% fees for every buy and sell. 8% of that goes to capstrategy.ton and 2% goes to the team. All 100% transparent on the TON blockchain. Once we have enough fees to buy the floor Durov's Cap, we buy it and re-list it for 1.2x cost. You can s…

❤38custom 545630501236168763221custom 545620301118337156720custom 545626469979864339513🤯8

Showing the 12 most recent of 20 posts we hold for @DurovsCapStrategy. 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 — 55,556 of 1,340,412entries 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.

Mentions

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

Трощий в крипте🍀
@troschiy · 4,1432 postsORESHNIK
@oreshnikchannel · 911 postPepe Strategy
@PlushPepesStrategy · 4231 post

Names

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

Pepe Strategy
@PlushPepesStrategy · 4231 post

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

“Durovs Cap Strategy” (@DurovsCapStrategy), 1,035 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/DurovsCapStrategy.

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.