7 Aug 2026, 13:22 UTC14 viewsread 7 August 2026
Early CA dropping for the first 3 chads who DM: @eth_willis or @sir_williz We ape early & split profits 💰 Serious grinders only. LFG 🚀🔥
Channel
BASEBAM CHAD'S
@BaseBamChads
On this record: Growth · Engagement · Posts · Citations · Cite this entry
2,715subscribers
-1 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 | -1002699054622 |
|---|---|
| Type | Channel |
| Username | @BaseBamChads |
| Created | Between 1 April 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 2 times, most recently 6 September 2026 |
| On Telegram | t.me/BaseBamChads |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 00:48 | 2,715 | +6 |
| 29 Aug 2026, 15:55 | 2,709 | -4 |
| 26 Aug 2026, 16:54 | 2,713 | +1 |
| 23 Aug 2026, 23:18 | 2,712 | -3 |
| 20 Aug 2026, 06:06 | 2,715 | -3 |
| 17 Aug 2026, 11:39 | 2,718 | -5 |
| 13 Aug 2026, 22:28 | 2,723 | +6 |
| 10 Aug 2026, 19:23 | 2,717 | +1 |
| 7 Aug 2026, 16:31 | 2,716 | no change |
| 7 Aug 2026, 14:33 | 2,716 | first reading |
Engagement
20 posts held, back to 1 August 2026 — 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
7 Aug 2026, 13:21 UTC12 viewsread 7 August 2026
I got 3-5 good early CA today and it will hit 100x Who wants in too? Dm @eth_willis or @sir_williz
7 Aug 2026, 13:15 UTC14 viewsread 7 August 2026
Photo
💡 Set a custom PNL background with /pnlbg
6 Aug 2026, 14:00 UTC39 viewsread 7 August 2026
5 spot open only at 1SOL LIFETIME first 5 people to dm👇VIP dm. @eth_willis or @sir_williz the early bird catches the worm.🥇
6 Aug 2026, 13:48 UTC74 viewsread 7 August 2026
I will soon share the next 10x - 1000X+ and save the trenches… Are you ready? 👀
6 Aug 2026, 13:41 UTC38 viewsread 7 August 2026
Dropping early ca for the first 5 people to Dm: @eth_willis or @sir_williz LFG chads 10x - 1000x trade returns 🚀🚀🔥
6 Aug 2026, 11:22 UTC41 viewsread 7 August 2026
Photo
💎💎💎💎 Call made 41.18X First Call by eth_willis @ $23.25K (6d) 3XEe11RMNqNTka33ik2yEmr3siUWmFQWSESP9Ejepump
6 Aug 2026, 08:47 UTC40 viewsread 7 August 2026
Photo
🚀 $KLEF price increased 10.1x to 191.3K 1st [19d] • eth_willis • $18.9K ✍️Stop?: customise with /settings
4 Aug 2026, 13:13 UTC61 viewsread 7 August 2026
🔥 OnlyMarms [261x] ├ eth_willis └ 12.8K → 3.33M (10d) HBrfYZgeLKdSvBBGnGkvAK4563pq8oBGpgNFAaespump
3 Aug 2026, 04:19 UTC103 viewsread 7 August 2026
Photo
Not every signal becomes a 159x - Cleaner signals - Better filtering - More conviction That's why Premium focuses on quality over quantity.
2 Aug 2026, 21:41 UTC109 viewsread 7 August 2026
3 spot open only at 1SOL LIFETIME first 3 people to dm👇VIP dm. @eth_willis the early bird catches the worm.🥇
2 Aug 2026, 21:35 UTC95 viewsread 7 August 2026
Are you ready for the next runner🏃🏃🏃
Showing the 12 most recent of 20 posts we hold for @BaseBamChads. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“BASEBAM CHAD'S” (@BaseBamChads), 2,715 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/BaseBamChads.
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.