Telegram RegisterThe public register of Telegram

Channel

JB's Calls

@Jbscalls

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

43subscribers

+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-1002022288670
TypeChannel
Username@Jbscalls
DescriptionCheapest Calls in crypto only ever .1 eth for All calls all projects big or small. For calls or other services dm @Master_Dev_King @SephirothGemCalls
CreatedBetween 1 November 2023 and 11 December 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/Jbscalls

Growth

437 August 2026 — 43 subscribers10 August 2026 — 43 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 42–44 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 16:3143no change
7 Aug 2026, 11:1043first reading

Engagement

20 posts held, back to 11 December 2023the 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 15 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
27
Videos
8
Links
54

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.

Video runtime
1m 09s
Average length
35s

Measured directly from 2 videos 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.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁375.0%
125.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 4reactions 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 11 December 2023 to 15 June 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

5 Aug 2024, 07:46 UTCviews —

JB's Calls pinned «━━━━━┒ ┓┏┓┏┓┃See you in the next life ┛┗┛┗┛┃ ┓┏┓┏┓┃\😭/ ┛┗┛┗┛┃ / ┓┏┓┏┓┃ ノ) ┛┗┛┗┛┃ ┓┏┓┏┓┃ ┛┗┛┗┛┃ ┓┏┓┏┓┃ ┛┗┛┗┛┃ ┃┃┃┃┃┃ ┻┻┻┻┻┻»

5 Aug 2024, 07:46 UTC≈1,260 views2 reactionsread 10 August 2026

━━━━━┒ ┓┏┓┏┓┃See you in the next life ┛┗┛┗┛┃ ┓┏┓┏┓┃\😭/ ┛┗┛┗┛┃ / ┓┏┓┏┓┃ ノ) ┛┗┛┗┛┃ ┓┏┓┏┓┃ ┛┗┛┗┛┃ ┓┏┓┏┓┃ ┛┗┛┗┛┃ ┃┃┃┃┃┃ ┻┻┻┻┻┻

😁2

8 Apr 2024, 01:31 UTC≈1,450 viewsread 10 August 2026

https://x.com/alfadao_/status/1777138202085601512?s=46&t=inNKVCVXetRNgWlnHh4izw

29 Mar 2024, 10:37 UTC≈1,340 views1 reactionsread 10 August 2026
Photo

🤖 Staking Update UX FIX 🤖 We are ready to share with you our latest staking updates. 1️⃣ Over 10% of all tokens are staked, with the majority of them for 60 days. 2️⃣ 8.5% of all tokens are burned, while 7.5% are being held by the team for rewards. 3️⃣ This currently takes out 26% of the GuardAI Supply. This illustrates the trust our community has in our project. 🤖 Updates about the UX in staking: We resolve

1

28 Mar 2024, 10:56 UTC875 viewsread 10 August 2026
Photo

We are going to have our next AMA on Friday 2pm UTC with @mad_apes. Mad Apes is going to announce it tomorrow officially, and remind everyone in in group 1 hour before our AMA takes part. Join us on Friday, while we are getting the word out. Our Twitter Post: https://x.com/BuyGuardBot/status/1773131019710779583?s=20

28 Mar 2024, 09:28 UTC733 viewsread 10 August 2026
Photo

🤖 We are happy to announce our strategic partnership with @unidexai! UniDexAI is a AI web3 trading platform that amalgamates essential features necessary for traders to make well-informed and time-sensitive trading decisions. We will be integrating their DEX into BuyGuardBot and adding their links to our Telegram. In return, $GUAI will be listed on unidexai.io and they will be providing us with banner advertisement

26 Mar 2024, 10:38 UTCviews —

JB's Calls pinned «GuardAI Buy! 🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳 💵 3 ETH ($10983.57) 🪙 4,135 GuardAI 💳 0xf178...d050 | Txn ⏫ Position +34.84% 🔘 Market Cap $2,205,640 📊 Chart ✨ Trade 🔔 Events 🔷 Safetrend…»

26 Mar 2024, 10:37 UTC474 viewsread 10 August 2026

GuardAI Buy! 🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳🐳 💵 3 ETH ($10983.57) 🪙 4,135 GuardAI 💳 0xf178...d050 | Txn ⏫ Position +34.84% 🔘 Market Cap $2,205,640 📊 Chart ✨ Trade 🔔 Events 🔷 Safetrend 💎 Trending 🥇 ETH SAFETREND 🔐 Safety Score: 100 | 100 🟢

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

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.

“JB's Calls” (@Jbscalls), 43 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Jbscalls.

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.