Telegram RegisterThe public register of Telegram
Telegram profile photo for BASED DEGEN GEMS

Channel

BASED DEGEN GEMS

@BasedDegenGems

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

2,744subscribers

-30 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-1001992057930
TypeChannel
Username@BasedDegenGems
CreatedBetween 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/BasedDegenGems

Growth

2,7442,7742,7597 August 2026 — 2,774 subscribers7 August 2026 — 2,774 subscribers8 August 2026 — 2,773 subscribers11 August 2026 — 2,766 subscribers15 August 2026 — 2,769 subscribers18 August 2026 — 2,765 subscribers21 August 2026 — 2,763 subscribers24 August 2026 — 2,764 subscribers27 August 2026 — 2,757 subscribers30 August 2026 — 2,756 subscribers2 September 2026 — 2,753 subscribers6 September 2026 — 2,744 subscribers7 August 20266 September 2026
12 measurements spanning 30 days, net -30. 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 2,740–2,779 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 19:162,744-9
2 Sept 2026, 11:542,753-3
30 Aug 2026, 22:352,756-1
27 Aug 2026, 22:082,757-7
24 Aug 2026, 19:592,764+1
21 Aug 2026, 12:162,763-2
18 Aug 2026, 06:022,765-4
15 Aug 2026, 00:152,769+3
11 Aug 2026, 14:142,766-7
8 Aug 2026, 10:342,773-1
7 Aug 2026, 12:012,774no change
7 Aug 2026, 11:592,774first reading

Engagement

20 posts held, back to 30 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
150.0%
😍150.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 3 of the 20 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 30 June 2026 to 31 July 2026, 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

31 Jul 2026, 17:02 UTC97 views1 reactionsread 7 August 2026
Photo

MEWTHREE | $117.8K A7BPmgCwt7WufzwhrPuRTvZgaovyPfRA2narLcjLpump View Chart: 🦅 Dexscreener | 📈 Defined Socials: 🐦 Twitter 🌐 Website Quick Buy: 🔺 Axiom | ☀️ Photon | 🔍 GMGN 💊 Padre | 🤖 Maestro | 🍌 Banana 🏛️ Trojan | 🟦 Based | ✳️ Sigma

😍1

11 Jul 2026, 11:30 UTC294 viewsread 7 August 2026

Name: Lizard (LIZARD) CA: 347k5f1WLRYe81roRcLBWDR6k3eCRunaqetQPW6pbonk Network: solana Total Supply: 999777379.812728 Circulating Supply: 999777379.812728 Markets Raydium | Socials Website | Telegram | Twitter | Explorer | CoingeckoPlease note that this may not be the accurate coin. Its ticker matches with the closest coin in Coingecko. Do your own research weather this is the right token or not

11 Jul 2026, 11:30 UTC269 viewsread 7 August 2026

$LIZARD Name: LIZARD Symbol: $LIZARD CA: 7NTs9FPw7tP2Bfjcn8eAJZUr4ApG8n9ZbXkT7Adwpump Market Cap: $194K https://theinterlocution.com ✔️ CheckDex.xyz ✔️ ✅ DexScreener PAID! ✅

7 Jul 2026, 19:55 UTC266 views1 reactionsread 7 August 2026
Photo

LYNK | $990.8K 9MetwAYBZWmsbJT56TDPLnuH5mnt6Evjwx1hNu6Epump View Chart: 🦅 Dexscreener | 📈 Defined Socials: 🐦 Twitter Quick Buy: 🔺 Axiom | ☀️ Photon | 🔍 GMGN 💊 Padre | 🤖 Maestro | 🍌 Banana 🏛️ Trojan | 🟦 Based | ✳️ Sigma

1

7 Jul 2026, 17:51 UTC173 views0 reactionsread 7 August 2026
Photo

MESSIGOAT | $380.7K J2Yv2umBhjP2Q7xT5tkYK4cceogqgkVrGXvb3a35pump View Chart: 🦅 Dexscreener | 📈 Defined Socials: 🐦 Twitter 🌐 Website Quick Buy: 🔺 Axiom | ☀️ Photon | 🔍 GMGN 💊 Padre | 🤖 Maestro | 🍌 Banana 🏛️ Trojan | 🟦 Based | ✳️ Sigma

30 Jun 2026, 23:04 UTC207 viewsread 7 August 2026
Video

Achievement Unlocked: x4! 🖖 @BasedDegenGems made a x4+ call on Luke Belmar. $3.7M ➡️ $15M 👁 View Call 📊 View Stats ➡️Auto-buy and sell calls like this through SpyDefi Filters!

30 Jun 2026, 23:04 UTC187 viewsread 7 August 2026
Video

Achievement Unlocked: Conviction! 👩‍🎓 @BasedDegenGems had the conviction to call Nest at a higher marketcap and it just hit x2+. $5.4M ➡️ $11M 👁 View Call 📊 View Stats 🔹 ELON - TRENDING #2

30 Jun 2026, 23:03 UTC134 viewsread 7 August 2026
Video

Achievement Unlocked: x2! ✌️ @BasedDegenGems made a x2+ call on The Solana Bull. $320K ➡️ $665K 👁 View Call 📊 View Stats ➡️Auto-buy and sell calls like this through SpyDefi Filters!

30 Jun 2026, 21:34 UTC115 viewsread 7 August 2026
Photo

bitcointalk | $109.4K FN6gjpTxsJGt5ZmwwYuxenHTWJhLT5wtXTV6fcP4pump View Chart: 🦅 Dexscreener | 📈 Defined Socials: 🐦 Twitter Quick Buy: 🔺 Axiom | ☀️ Photon | 🔍 GMGN 💊 Padre | 🤖 Maestro | 🍌 Banana 🏛️ Trojan | 🟦 Based | ✳️ Sigma

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

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.

Named by

Channels on the register whose posts name this channel's handle.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Auto Forward Telegram BOT News
@Auto_Forward_Messages · 111,374
Telegram ranks this channel #8 of 43 here — alongside 42 others — read 21 August 2026
𝐁𝐫𝐨𝐨𝐤 𝐂𝐚𝐥𝐥𝐬 🐧
@brookcalls · 32,109
Telegram ranks this channel #16 of 79 here — alongside 78 others — read 7 September 2026
Chads’ Meme Alliance: 100X
@memetakeovers · 71,249
Telegram ranks this channel #30 of 67 here — alongside 66 others — read 22 August 2026
Profit Crypto Calls
@Profittrde · 35,277
Telegram ranks this channel #36 of 72 here — alongside 71 others — read 2 September 2026
Meta caller
@metacaller · 43,115
Telegram ranks this channel #74 of 78 here — alongside 77 others — read 3 September 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“BASED DEGEN GEMS” (@BasedDegenGems), 2,744 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/BasedDegenGems.

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.