🤑 #FameEX 平台 $TCAP 上币空投活动来啦! @TcapFund 立即參与并瓜分100,000 $TCAP 空投💰 1️⃣ 完成首次任意金额 $TCAP 现货交易,即可得 5 USDT 体验金 2️⃣ $TCAP 现货累计交易量 ≥200 USDT 即可参与瓜分100K TCAP奖池。 交易越多,空投越多! 🎁 更多详情 🔽 fameex.com/zh-CN/announce… https://x.com/fameexzh/status/1778363952805888130?s=46&t=ptQ37VurofKypN1y1earKg

Channel
TCAP_Token (BRC20)
@TCAP_Token
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
8subscribers
+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 | -1002131574425 |
|---|---|
| Type | Channel |
| Username | @TCAP_Token |
| Description | Official TCAP Token TG Channel Tokenised Digital Assets Hedge Fund. Exploring Digital Assets & Real World Assets Opportunities. TG Chat: https://t.me/TCAP_Token_Chat Website: https://tcaptoken.com/ X: https://twitter.com/TcapFund |
| Created | 16 March 2024 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/TCAP_Token |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 14:16 | 8 | no change |
| 7 Aug 2026, 12:28 | 8 | first reading |
Engagement
15 posts held, back to 16 March 2024 — 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 15 posts for this entry, the most recent from 11 April 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 4
- Links
- 9
Lifetime counters from Telegram’s own channel header, read 12 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
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 2 | 100.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 1 of the 15 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 16 March 2024 to 11 April 2024, 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
🤑 #FameEX New Listing $TCAP Event! @TcapFund Join now to share the 100,000 $TCAP airdrops 💰 1️⃣ First $TCAP trade of any amount to grab 5 USDT trial fund 2️⃣ Trade $TCAP spot ≥200 USDT to share the 100K TCAP prize pool. More details🔽 fameex.com/en-US/announce… #giveaway #bonus https://x.com/fameexglobal/status/1778363768147493299?s=46&t=ptQ37VurofKypN1y1earKg
✅ We've listed on Coinpaprika platform. 🔥 Learn more about #TCAP #BRC20 and follow link👇 https://coinpaprika.com/coin/tcap-tcap/#!widget
https://x.com/tcapfund/status/1775487481577685158?s=46&t=ptQ37VurofKypN1y1earKg
https://x.com/fameexglobal/status/1774723206269825315?s=46&t=ptQ37VurofKypN1y1earKg
https://x.com/fameexzh/status/1774703151754711252?s=46&t=ptQ37VurofKypN1y1earKg
✅ We've listed on @CoinCodex platform. 🤝 The $TCAP token sale is currently in its first stage. 🔥 Stay tuned for events with our @FameEXGlobal new #listing partner! 👉 https://coincodex.com/crypto/tcap/ 👉 https://x.com/TcapFund/status/1772252429381181604?s=20
🔥 FameEX new #listing partnership: @TcapFund $TCAP is the first native token built on BRC20 Bitcoin's Ordinals protocol of an institutional-grade tokenized Digital Assets Hedge Fund. #TCAP aims to onboard institutional & high net worth sophisticated investors into the emerging world of Digital Assets and drive innovation in the tokenization of Real World Assets (RWA). 🤝 Stay tuned for events with our new partner! …
🔥2
/connect @RoseSupportChat
/welcome on
Welcome to Rose! Rose is primarily a group management bot, and has limited functionality in channels. Channel features include: - Log channels - Fed logs - Joining federations
TCAP_Token (BRC20) pinned «#1 Welcome to our Official TCAP Token TG Channel About us: Tokenised Digital Assets Hedge Fund. Exploring Digital Assets & Real World Assets Opportunities. Website: https://tcaptoken.com/ X: https://twitter.com/TcapFund TG: https://t.me/TCAP_Token»
Showing the 12 most recent of 15 posts we hold for @TCAP_Token. 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
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@TCAP_Token named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“TCAP_Token (BRC20)” (@TCAP_Token), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/TCAP_Token.
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.