Telegram RegisterThe public register of Telegram
Telegram profile photo for YAE CALLS 🌸 | ALLCHAIN

Channel

YAE CALLS 🌸 | ALLCHAIN

@YaeCalls

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

44subscribers

-2 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-1001525216362
TypeChannel
Username@YaeCalls
CreatedBetween 1 August 2021 and 14 September 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live8 October 2026
Measurements held3
Confirmed unchanged2 times, most recently 8 October 2026
On Telegramt.me/YaeCalls

Topic

Other / unclassifiable — 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 45% 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

4446457 August 2026 — 46 subscribers10 August 2026 — 46 subscribers27 September 2026 — 44 subscribers7 August 202627 September 2026
3 measurements spanning 51 days, net -2. 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 44–46 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Sept 2026, 14:5844-2
10 Aug 2026, 14:1646no change
7 Aug 2026, 04:0646first reading

Engagement

20 posts held, back to 14 September 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 19 September 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

14 Sept 2023, 12:28 UTC137 viewsread 10 August 2026

https://t.me/MobyOfficial Launch Today 4PM UTC

Signed Yellow Flamingo

2 Dec 2022, 20:10 UTC592 viewsread 10 August 2026

NEW COMMUNITY BSC OLD SCHOOL 💩 Make SHIDO INU and Hay work as One. ✅ Low Marketcap Gem $300 MC NOW ❇️ NFA DYOR ☎️Telegram : @HaySHIDO 📄 CHART ⚡️https://poocoin.app/tokens/0x4f25235503d9e05df87cda087644bf03f4f37b6d 📄Contract Address ⚡️ 0x4f25235503d9e05df87cda087644bf03f4f37b6d ✅ LP Locked 1 Year 🔒 https://mudra.website/?certificate=yes&type=0&lp=0x98d93b7a53f4fadd85bef136e86eeb7a203199dd ⚡️ Renounced https://bs…

28 Nov 2022, 23:11 UTC466 viewsread 10 August 2026

AppElon just launched on BSC based on elon fighthing Apple and being trending on twitter.🔵 🔹 Stealth launched 🔹Low max tx & Max wallet at launch 🔹Organic growth 🔹Building community and stable floor. 🔹Nice marketing strategy to push and keep the floor. 🔹Low tax 🔹Safe dev Join our community and help us building the next moonshot 💎 Telegram: @AppElonBSC Chart: https://poocoin.app/tokens/0x26e6621d2b8d27c4436cf961bb5…

28 Oct 2022, 15:43 UTC517 viewsread 10 August 2026
Photo

APTOS CHAIN NFT Still early.. Easy to get whitelist Slurponomics and DeFi mechanics. Some appear cute, some look slurpy, some are from another planet! Maybe some even look familiar! Twitter: https://twitter.com/SlurpDoges Discord: https://discord.gg/qFCENaPMZ8 Still early.. Easy to get whitelist

19 Oct 2022, 17:37 UTC486 viewsread 10 August 2026

How to BRIDGE (APTOS): 1. Buy APTOS on CEXs that support it. » You may check here: https://coinmarketcap.com/currencies/aptos/markets/ 2. Send your APTOS to your Aptos Wallet Use one of these wallets: https://martianwallet.xyz/ https://fewcha.app/ https://petra.app/ 3. DEX's that support APTOS: aptoswap.net animeswap.org https://liquidswap.com/#/ #DYOR

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

“YAE CALLS 🌸 | ALLCHAIN” (@YaeCalls), 44 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/YaeCalls.

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.