Telegram RegisterThe public register of Telegram
Telegram profile photo for Base Token Tracker

Channel

Base Token Tracker

@Basetokentracker

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

178subscribers

-2 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-1001569826840
TypeChannel
Username@Basetokentracker
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live21 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/Basetokentracker

Growth

1781801797 August 2026 — 180 subscribers8 August 2026 — 180 subscribers15 August 2026 — 179 subscribers21 August 2026 — 178 subscribers7 August 202621 August 2026
4 measurements spanning 14 days, net -2. 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 178–180 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 06:46178-1
15 Aug 2026, 03:08179-1
8 Aug 2026, 13:02180no change
7 Aug 2026, 10:56180first reading

Engagement

20 posts held, back to 12 May 2024the 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 7 August 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2s
Average length
2s

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.

Recent posts

7 Aug 2024, 05:02 UTC134 viewsread 8 August 2026
Video

Trending Ecosystem: 📈📈 🔹 ETH SCAN TRENDING 💎 TON SCAN TRENDING 🔵 BASE SCAN TRENDING 🪙 SOL SCAN TRENDING

7 Aug 2024, 05:02 UTCviews —

Base Token Tracker pinned «JOIN EVENT CHANNEL TO BUY TOKENS EARLY https://t.me/TrendingEvent»

7 Aug 2024, 05:02 UTC134 viewsread 8 August 2026
Forwarded from @RHTRENDINGLIVE

JOIN EVENT CHANNEL TO BUY TOKENS EARLY https://t.me/TrendingEvent

6 Jul 2024, 08:21 UTC145 viewsread 8 August 2026
Forwarded from @RHTRENDINGLIVEVideo

✅ NEW UPDATE !! ✅ We are now working with maestro so we upgraded from raydium trending to maestro trending and we have new good features coming buy bot + trading bot and also refer to earn we are hosting the bot probably soon if you’re interested in working with us dm @Giga100X ✅ ➡️➡️➡️➡️➡️➡️➡️➡️➡️

12 May 2024, 17:37 UTC265 viewsread 8 August 2026

Nyan Cat | $NYAN 0x53BD950312D83EFef6b985F65764ce9177E65a45 TotalSupply:100000000.0 Telegram : Charts : Dexscreener

12 May 2024, 17:37 UTC239 viewsread 8 August 2026

ElephenFrenchMoon | $ELFM 0xb4a4D3fda2E791164033944D07d07bDD84813CF6 TotalSupply:111000000.0 Telegram : Charts : Dexscreener

12 May 2024, 17:37 UTC195 viewsread 8 August 2026

avocadians | $AVO 0xE3364225f3f6832E0521eFE48848A37A2f20fC9c TotalSupply:100000000.0 Telegram : Charts : Dexscreener

12 May 2024, 17:37 UTC152 viewsread 8 August 2026

Justin Baseber | $JB 0x11Bf8CeebFaCBC28006B3b0A0c6bfb720CFfAe30 TotalSupply:69000000000.0 Telegram : Charts : Dexscreener

12 May 2024, 17:36 UTC122 viewsread 8 August 2026

Puff Bloo 3.0 | $PUFFBLOO3.0 0x9d97Bd8962f860DC394D8Ee5F708962D613E7041 TotalSupply:1000000000.0 Telegram : Charts : Dexscreener

Showing the 12 most recent of 20 posts we hold for @Basetokentracker. 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

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“Base Token Tracker” (@Basetokentracker), 178 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/Basetokentracker.

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.