Telegram RegisterThe public register of Telegram
Telegram profile photo for JointCalls

Channel

JointCalls

@JointCalls

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

3subscribers

-1 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-1001759711449
TypeChannel
Username@JointCalls
CreatedBetween 1 December 2021 and 15 March 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live8 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/JointCalls

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 8 October 2026 and assigned it the closest of 31 fixed categories, at 95% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

343.57 August 2026 — 4 subscribers13 August 2026 — 4 subscribers8 October 2026 — 3 subscribers7 August 20268 October 2026
3 measurements spanning 62 days, net -1. 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 3–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 15:203-1
13 Aug 2026, 04:324no change
7 Aug 2026, 04:404first reading

Engagement

20 posts held, back to 15 March 2022 — 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 2 July 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Jul 2023, 04:51 UTCviews —

The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 28 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

13 Jun 2022, 23:53 UTCviews —

JointCalls pinned «Play of my friends, just launched. Biggest buy event ongoing, easy x10 i think. It have a good mechanism that we have to feed the kraken, and kraken will make buys, buys and more buys while tokens burn. Contract: 0xb9b06ac9d1df45fc25cf6695998ea10a5b0b7d55…»

13 Jun 2022, 23:53 UTC13 viewsread 13 August 2026

Play of my friends, just launched. Biggest buy event ongoing, easy x10 i think. It have a good mechanism that we have to feed the kraken, and kraken will make buys, buys and more buys while tokens burn. Contract: 0xb9b06ac9d1df45fc25cf6695998ea10a5b0b7d55 Chart: https://poocoin.app/tokens/0xb9b06ac9d1df45fc25cf6695998ea10a5b0b7d55 Tg: @OfficialKrakenToken

10 Jun 2022, 00:16 UTCviews —

JointCalls pinned «CHROMA Buy! 🟢🟢🟢🟢🟢🟢 Spent: $29.51 (0.1 BNB) Got: 506,669,216 CHROMA Buyer Position: New! Price: 0.00000005823 (0.0000000002042 BNB) MCap: $581 https://poocoin.app/tokens/0x416a2dc7213cdbbb07d182c148f32c40373cdd0a 💎@CHROMATOKEN💎»

10 Jun 2022, 00:16 UTC17 viewsread 13 August 2026

CHROMA Buy! 🟢🟢🟢🟢🟢🟢 Spent: $29.51 (0.1 BNB) Got: 506,669,216 CHROMA Buyer Position: New! Price: 0.00000005823 (0.0000000002042 BNB) MCap: $581 https://poocoin.app/tokens/0x416a2dc7213cdbbb07d182c148f32c40373cdd0a 💎@CHROMATOKEN💎

22 Apr 2022, 22:05 UTC23 viewsread 13 August 2026

https://twitter.com/cro_finger/status/1517613892222033920 💚💚50 CRO GIVEAWAY.💚💚 Steps: 1) Follow us on twitter: https://twitter.com/cro_finger 2) Join our TG community: http://t.me/crofinger 3) RT and Fav this tweet Winner announcement will be done day 26/04/2022

26 Mar 2022, 02:13 UTCviews —

JointCalls pinned «🐊CroZilla - 鳄鱼 First token on bsc who support our own doubler.🤑 With doubler taxes of Crozilla token we inject every 2 hours all the taxes generated into the doubler contract. That will support the doubler and all of you will get paid. That will be so fucking…»

26 Mar 2022, 02:13 UTC62 viewsread 13 August 2026

🐊CroZilla - 鳄鱼 First token on bsc who support our own doubler.🤑 With doubler taxes of Crozilla token we inject every 2 hours all the taxes generated into the doubler contract. That will support the doubler and all of you will get paid. That will be so fucking amazing👀. Minimum bnb to send to Doubler Contract: 0.01 bnb Maximum bnb to send to Doubler Contract: 1 bnb X2 of your contribution. 👇Tokenomics of CroZi…

24 Mar 2022, 05:24 UTCviews —

JointCalls pinned «$MAPE - MiniApe New generation of Ape Contract : 0x384c0daefcdbf11f4f62b9cddc571640a98d0a2f Telegram: @MiniApe_bsc Chart: https://poocoin.app/tokens/0x384c0daefcdbf11f4f62b9cddc571640a98d0a2f»

24 Mar 2022, 05:23 UTC45 viewsread 13 August 2026

$MAPE - MiniApe New generation of Ape Contract : 0x384c0daefcdbf11f4f62b9cddc571640a98d0a2f Telegram: @MiniApe_bsc Chart: https://poocoin.app/tokens/0x384c0daefcdbf11f4f62b9cddc571640a98d0a2f

22 Mar 2022, 15:37 UTCviews —

JointCalls pinned «T.me/bigmoneydoubler Ponzi system X2 of your investment Contract for deposit. 0x74ad0175c7fD2D10cDbF8471D1a8731733876699 No mininum. Maximum 0.5 bnb»

22 Mar 2022, 15:37 UTC58 viewsread 13 August 2026

T.me/bigmoneydoubler Ponzi system X2 of your investment Contract for deposit. 0x74ad0175c7fD2D10cDbF8471D1a8731733876699 No mininum. Maximum 0.5 bnb

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

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

“JointCalls” (@JointCalls), 3 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/JointCalls.

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.