Telegram RegisterThe public register of Telegram
Telegram profile photo for ASHES CALLS 🟢 BSC|ETH ✨

Channel

ASHES CALLS 🟢 BSC|ETH ✨

@Ashescalls

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

41subscribers

-3 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-1001942954505
TypeChannel
Username@Ashescalls
CreatedBetween 1 April 2023 and 20 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live3 October 2026
Measurements held5
Confirmed unchanged3 times, most recently 3 October 2026
On Telegramt.me/Ashescalls

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 29 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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

414442.57 August 2026 — 44 subscribers10 August 2026 — 44 subscribers20 August 2026 — 43 subscribers1 September 2026 — 42 subscribers10 September 2026 — 41 subscribers7 August 202610 September 2026
5 measurements spanning 34 days, net -3. 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 41–44 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 03:5541-1
1 Sept 2026, 16:2642-1
20 Aug 2026, 05:1543-1
10 Aug 2026, 16:0044no change
7 Aug 2026, 09:4044first reading

Engagement

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

Reaction mix

37 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 54.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2054.1%
🍌513.5%
❤38.11%
🫡38.11%
🆒12.70%
🍓12.70%
👌12.70%
👍12.70%
👏12.70%
😨12.70%

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 8 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 37 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 20 April 2023 to 12 May 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

12 May 2025, 07:45 UTCviews —

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

24 Apr 2023, 10:52 UTCviews —

ASHES CALLS 🟢 BSC|ETH ✨ pinned «Good morning gang weekend was very slow let’s see what Monday brings shill me your hot gems 💎»

24 Apr 2023, 10:51 UTC≈3,580 views3 reactionsread 10 August 2026

Good morning gang weekend was very slow let’s see what Monday brings shill me your hot gems 💎

🔥1🫡1😨1

23 Apr 2023, 19:08 UTC≈2,770 views11 reactionsread 10 August 2026
Photo

✨ CULTURAL CALL ✨ ETH PLAY Been watching these apes 🦍 for a while now 💎 and been sent it a few times in my dm 🚀 it’s not a small market cap play it’s long term 🔥 Mc 1.8M https://www.dextools.io/app/ether/pair-explorer/0xa67ceebf094b32ff3313f9a63150c74792a1acdc https://t.me/MONKEYS_ERC

🔥11

23 Apr 2023, 18:35 UTC≈1,950 viewsread 10 August 2026
Photo

✨ update on scarcity project ✨ Called at 30k it hit ath around 65k on a correction now but the team and community have been pushing this project since launch so probably good to catch the dip 🚀 They have a unique burn function 🔥 https://t.me/TheScarcityProject

23 Apr 2023, 13:11 UTCviews —

ASHES CALLS 🟢 BSC|ETH ✨ pinned «Good morning gang slow weekend didn’t see much I liked yesterday maybe today will be different shill me your gems 💎 🚀»

23 Apr 2023, 13:11 UTC≈2,680 views2 reactionsread 10 August 2026

Good morning gang slow weekend didn’t see much I liked yesterday maybe today will be different shill me your gems 💎 🚀

🍌1🫡1

22 Apr 2023, 12:03 UTC≈2,470 views2 reactionsread 10 August 2026

Good morning apes 🚀 On the hunt for todays banger shill me what’s mooning or has potential ✨

🔥2

22 Apr 2023, 11:32 UTCviews —

ASHES CALLS 🟢 BSC|ETH ✨ pinned «✨CULTURAL CALL ✨ Looks good community seem hyped 🚀 Ape scale 8/10 💎 Mc 60k Time your entry 🔥 https://t.me/blindape_bsc»

22 Apr 2023, 11:32 UTC≈2,310 views1 reactionsread 10 August 2026

✨CULTURAL CALL ✨ Looks good community seem hyped 🚀 Ape scale 8/10 💎 Mc 60k Time your entry 🔥 https://t.me/blindape_bsc

👍1

Showing the 12 most recent of 20 posts we hold for @Ashescalls. 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 September 2026 — this entry's latest reading, not the date you are reading this.

“ASHES CALLS 🟢 BSC|ETH ✨” (@Ashescalls), 41 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/Ashescalls.

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.