Telegram RegisterThe public register of Telegram

Channel

Bazz degen callz

@bazzcallz

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

38subscribers

+0 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-1002258193541
TypeChannel
Username@bazzcallz
DescriptionContact @DIBme3 or @Papar_hands_Mark for any type of queries……. Nothing in this channel should be considered financial advice.
Created19 October 2024measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/bazzcallz

Growth

387 August 2026 — 38 subscribers10 August 2026 — 38 subscribers7 August 202610 August 2026
2 measurements spanning 3 days. 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 37–39 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 20:4638no change
7 Aug 2026, 14:0338first reading

Engagement

19 posts held, back to 19 October 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 19 posts for this entry, the most recent from 23 January 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
11
Links
11

Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

117 reactions across 13 posts, in 7 distinct kinds. The most used accounts for 51.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥6051.3%
2723.1%
🍾119.40%
👍86.84%
👏65.13%
🎉32.56%
❤‍🔥21.71%

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 13 of the 19 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 117reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 19 October 2024 to 23 January 2025, 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

23 Jan 2025, 17:22 UTC138 views2 reactionsread 10 August 2026
Photo

Bshop is looking strong! Just broke ath!

2

18 Jan 2025, 19:56 UTC149 views2 reactionsread 10 August 2026
Photo

Time to grab some $BSOP tonight. Experienced team crushing it on Base, building with AI agents ready to dominate. They hit millions in the bear market imagine the bull. $BSOP is launching today. Telegram Agents go live soon, and the X Agent reveal is just around the corner. Don’t miss your chance to get in early. Join their Telegram for today’s launch at 8 PM UTC! AI agents + building on base + experienced team o

2

23 Nov 2024, 21:22 UTC250 views11 reactionsread 10 August 2026

1000x by Clanker on a dip. Sitting at 60k mc. Have conviction this play will do well in the coming months. Loads of familiar faces in the tg. https://dexscreener.com/base/0x397af86a35288f7A219febAab34F9b947d4d772D

🔥72❤‍🔥2

18 Nov 2024, 12:40 UTC269 views15 reactionsread 10 August 2026
Photo

1000x by clanker! 170k mc this can be a sendor https://dexscreener.com/base/0x397af86a35288f7A219febAab34F9b947d4d772D

🔥84🍾2👍1

8 Nov 2024, 19:09 UTC202 views9 reactionsread 10 August 2026

New launch strong team 💪 Based meme.... Pepe might be dead, but he will go to heaven! https://dexscreener.com/base/0xdc85356c99e516DED55b0C435a081c398A8424d9

🔥5🍾2👍2

27 Oct 2024, 18:30 UTC≈1,170 viewsread 10 August 2026
Photo

Hi guys! The old $BLUE tg was mass reported and deleted. Join the new one here https://t.me/BlueBlueBase All team still here and as determined to send it .

27 Oct 2024, 12:30 UTC149 views4 reactionsread 10 August 2026

Over 60x for $BLUE since first call . Team is doing a fantastic job and the chart reflects it!

🔥21👍1

27 Oct 2024, 12:29 UTC115 viewsread 10 August 2026
Photo

BLUE ✅ Buy! 🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦 💵 0.047 ETH ($117.23) 🪙 74,407 BLUE 🪙 0x7cb2…6b4f | Txn 🔼 Position +8.74% 🔼 Market Cap $1,522,815 📊 Chart 🔵 Trade 🔵 Trending 🟢 Trending 🥇 BASE TRENDING

26 Oct 2024, 07:31 UTC110 views8 reactionsread 10 August 2026
Photo

Should problably start focusing on other tokens but the $BLUE chart is to beautiful to ignore... Another day, another ATH for the 6th consecutive day. https://dexscreener.com/base/0x03623367f4a833f23e8c917b3448dd31805e3d07

5👍2🔥1

25 Oct 2024, 23:05 UTC82 views12 reactionsread 10 August 2026
Photo

BLUE ✅ Buy! 🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦 💵 0.05 ETH ($121.86) 🪙 191,971 BLUE 🪙 0xa172…8967 | Txn ✅ New Holder 🔼 Market Cap $635,329 📊 Chart 🔵 Trade 🔵 Trending 🟢 Trending 🥇 BASE TRENDING

🔥54🎉3

24 Oct 2024, 21:13 UTC98 views11 reactionsread 10 August 2026
Photo

New day, new ATH for $BLUE! 530K and going! https://dexscreener.com/base/0x03623367f4a833f23e8c917b3448dd31805e3d07

🔥53🍾3

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

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

“Bazz degen callz” (@bazzcallz), 38 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/bazzcallz.

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.