Yoo

Channel
ApeFate
@apeFate
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
36subscribers
-4 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 | -1001909282130 |
|---|---|
| Type | Channel |
| Username | @apeFate |
| Created | Between 1 March 2023 and 19 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/apeFate |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 21:52 | 36 | -1 |
| 14 Aug 2026, 20:58 | 37 | -2 |
| 10 Aug 2026, 20:01 | 39 | no change |
| 7 Aug 2026, 15:00 | 39 | -1 |
| 7 Aug 2026, 10:59 | 40 | first reading |
Engagement
19 posts held, back to 19 September 2023 — 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 19 posts for this entry, the most recent from 12 November 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
GM degens
What a boring week 😮💨
X3 - ticker -> $ETHEREUM Locked, renounced and tax 1/10 https://dexscreener.com/ethereum/0x26dd584fe01d4c67ec16efbe5dfd953b4eefea6e https://t.me/hpodvigs69inu10_eth Only bangers -> here
Launch soon: hpodvigs69inu10 Previous did well up to 700K mc DYOR https://t.me/hpodvigs69inu10_eth https://hpodvigs69inu10.fun 0x27f9aadefc14419bed2c5f013afb190fe6d2c566 Only bangers -> here
$BBFWEN just launched 24K mc locked renounced 1/1 https://dexscreener.com/ethereum/0x41d39a87ce9718cfd53236ed3dbbbd4ddb3dd700 https://t.me/BABYFWEN Only bangers -> here
Update - $RITTY Called at 205k mc, we did a good x3. Yesterday, we've got a nice dip at ≈ 300k and now back to 415k mc. Accumulating for the next step. 28k volume in the past 1H, waiting for Monday pump. https://t.me/RoaringKittyERC https://dexscreener.com/ethereum/0x6ef2db22142107a15fcb205e3bf84db86661a1a2 Only bangers -> here
X3 - $RITTY MC: 640k 1M volume (24H) Lp burnt https://t.me/RoaringKittyERC https://dexscreener.com/ethereum/0x6ef2db22142107a15fcb205e3bf84db86661a1a2 Only bangers -> here
$RITTY Pumping, waiting for a dip Tax: 1/1 MC: 205k Renounced and locked https://t.me/RoaringKittyERC https://dexscreener.com/ethereum/0x6ef2db22142107a15fcb205e3bf84db86661a1a2
$OPOX eca leaked so -> quickplay LP locked, renounced Tax: 0/0 MC: 30k https://t.me/OPOXeth https://www.dextools.io/app/en/ether/pair-explorer/0xc711af62FDbBFd06AB89D0726DfFA655b6321AaB Only bangers -> here
$PepeNeverDie eca: 0x9320dd4104624220673cceb17a0641a774617a54 https://t.me/PepeNeverDieerc https://pepeneverdie.live
ApeFate pinned «A few things you need to know: - I only give essential information about the projects I post. Short post = effective post. - No need to post charts, if you want to invest, go find a good entry all by yourself. My posts are NFA - Prelaunch posts are the…»
Showing the 12 most recent of 19 posts we hold for @apeFate. 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
- 3
- 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
- 3
- vacant every time we have ever looked
@apeFate named 3 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 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“ApeFate” (@apeFate), 36 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/apeFate.
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.