Channel
@FightClubApe
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
17subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002064051513 |
|---|---|
| Type | Channel |
| Username | @FightClubApe |
| Created | 10 March 2024 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/FightClubApe |
Crypto & trading — 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 3 October 2026 and assigned it the closest of 31 fixed categories, at 95% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 00:41 | 17 | -1 |
| 11 Aug 2026, 18:31 | 18 | no change |
| 7 Aug 2026, 12:36 | 18 | first reading |
19 posts held, back to 10 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 page 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 19 posts for this entry, the most recent from 12 January 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
⚡️ https://trojan.com/@milady ⚡️ (Sign up here and get a boosted ref + $50 for signing up) So why Trojan: -Lowest fees (~0.6%) -Highest cashback -5-tier referral system (Axiom is 2 tiers) -DCA orders -Copy trading At a minimum, I suggest you give it a try. You have nothing to lose, and you get $50 free to trade with if you sign up using https://trojan.com/@milady
(🔥TON) 4TH Just launched, 10k area. $4TH, following 4th of July hype on TON. Know how these work. Be safe with entries. Degen. Dyor http://t.me/freeUSA_4th https://www.geckoterminal.com/ton/pools/EQByi9_evPQZFqu3LQD8ifix5kqtwhhHhDCDSNNJ4LjsvJF_ EQAeFtg4zsr-4kUFZLwMtqejJNuiLLN0-6Sgw2Z-7iqMTQbz
(🔥SOL) TIDDYS Okay guys i got a bag of $TIDDYS tbh i think this token can fly narrative is well goood https://t.me/tiddysSOL https://dexscreener.com/solana/2VLo6dMDZeVXPxTUbRiK6MKNg1oa1otjpe8KpBhzbofw
2x plus, 90k 🔥 now 70k $CROC 🔥
(🔥SOL) CrocDog Just going live, find safe entry. 40k area. Nice branding following dog meta. Links below. Risky degen, dyor. https://t.me/CrocDogSolana https://crocdog.xyz/ AcFPFzR2QJcPvc6CEK2p8QqhVzxUxVpbzAMQ723aJxXy
(🔥BASE) Ethereum Rush Reflections token. Earn ETH by holding at least 500k tokens every 10 minutes. 5/5 tax with 2% going to reward for holders. LP is locked 1 year. Chart at highs, find safe entry. Dyor https://t.me/EthereumRush https://www.ethrush.site 0xDeAD2De8581428829DB5698e37bD6E39a3C99f3E
4x plus, 110k 🔥 $THEO 🔥
(🔥ETH) The General Gambles Channel 🎲 New launch following BTC narrative hype and Nick Szabo tweet. Riskier degen as tweets can be volatile. 25k area. Links below, dyor LP Burnt, Renounced. 0/0 https://t.me/TheGeneralTheo https://thegeneraltheo.xyz/ 0x3c522221203916211af9f53d77b7b66cbab963b1 TRADE BOT
4.5x plus, 270k 🔥 now 223k $OLLIE 🔥
(🔥BASE) Ollie Dog Following Jogeco hype this is Fred Wilson from Coinbases' dog. At highs, find safe entry. Wait for tax/clog etc. Riskier degen, links below dyor https://t.me/OllieDogBase 0x24fCA802DadE850a7c4c8d29A921EDd603F746CE TRADE BOT
Sticker, posted without a caption
Ster Wers Buy! 🦾🦾🦾🦾🦾🦾🦾🦾🦾🦾🦾🦾🦾🦾🦾🦾🦾 💵 $155.95 (1 SOL) 🏷 243,365 STER WERS 👤 Buyer / TX 🪙 Position +14% 💲 Price $0.000640 ▶️ Market Cap $640,781 📈 Chart 🔥 Trending 💰 Buy
Showing the 12 most recent of 19 posts we hold for @FightClubApe. 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.
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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“Fight Club Apes” (@FightClubApe), 17 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/FightClubApe.
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.