Channel
@atlantes_calls
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,693subscribers
-70 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002215428459 |
|---|---|
| Type | Channel |
| Username | @atlantes_calls |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/atlantes_calls |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 18:38 | 1,693 | -8 |
| 13 Sept 2026, 16:01 | 1,701 | -2 |
| 9 Sept 2026, 16:16 | 1,703 | -3 |
| 3 Sept 2026, 23:37 | 1,706 | -3 |
| 31 Aug 2026, 15:06 | 1,709 | -7 |
| 28 Aug 2026, 22:07 | 1,716 | -5 |
| 26 Aug 2026, 03:42 | 1,721 | -9 |
| 20 Aug 2026, 02:22 | 1,730 | -6 |
| 16 Aug 2026, 20:38 | 1,736 | -5 |
| 13 Aug 2026, 04:03 | 1,741 | -14 |
| 10 Aug 2026, 08:47 | 1,755 | -6 |
| 7 Aug 2026, 16:52 | 1,761 | -2 |
| 7 Aug 2026, 15:48 | 1,763 | no change |
| 7 Aug 2026, 12:58 | 1,763 | first reading |
20 posts held, back to 4 February 2025 — 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 February 2025. An engagement rate over an empty window would be a number about nothing.
4 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 50.0% | |
| 👍 | 1 | 25.0% | |
| 🤝 | 1 | 25.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 4 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 4 February 2025 to 12 February 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.
$mcga | #mcga ---------------------------------- 🚨 Alert Time (UTC): 2025-02-12 20:22:23 ---------------------------------- 🔍 Token Overview: CA: 0xd71ccdc935afc207be92c333a8e480ea51bfde97 CA Age: 1m0s | Pair: 1m0s Block: 5 | Tick: 6 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $26.53k MCap: $82.94k | ATH: $137.72k MC/Liq Ratio: 3.13 Volume: $52.79k Tax: Buy 22% / Sell 22% --------…
❤2
$NEZHA | #NEZHA ---------------------------------- 🚨 Alert Time (UTC): 2025-02-12 14:58:47 ---------------------------------- 🔍 Token Overview: CA: 0x8619552e57a80325df4b8e685533c0eb1f68ab2e CA Age: 2m12s | Pair: 2m12s Block: 11 | Tick: 7 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $32.61k MCap: $104.05k | ATH: $149.18k MC/Liq Ratio: 3.19 Volume: $20.14k Tax: Buy 20% / Sell 0% ---…
$Duo | #Duo ---------------------------------- 🚨 Alert Time (UTC): 2025-02-12 11:36:35 ---------------------------------- 🔍 Token Overview: CA: 0xfcc5b806fb2e7046d58ff5d6b279e602d67bf769 CA Age: 4m24s | Pair: 2m12s Block: 11 | Tick: 6 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $32.54k MCap: $106.48k | ATH: $208.34k MC/Liq Ratio: 3.27 Volume: $26.60k Tax: Buy 3% / Sell 3% --------…
$HARRYBOLZ | #HARRYBOLZ ---------------------------------- 🚨 Alert Time (UTC): 2025-02-11 10:56:59 ---------------------------------- 🔍 Token Overview: CA: 0x570c414376fa07e63a6e5ca522ecb5acf984fa17 CA Age: 1m0s | Pair: 1m0s Block: 5 | Tick: 5 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $38.95k MCap: $142.22k | ATH: $257.37k MC/Liq Ratio: 3.65 Volume: $30.20k Tax: Buy 10% / Sell 0%…
$HARRYBOLZ | #HARRYBOLZ ---------------------------------- 🚨 Alert Time (UTC): 2025-02-11 10:12:47 ---------------------------------- 🔍 Token Overview: CA: 0xa85bf0da227aa5021c5512a38cef4814feab3a2f CA Age: 2m24s | Pair: 2m12s Block: 10 | Tick: 9 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $18.23k MCap: $39.67k | ATH: $79.11k MC/Liq Ratio: 2.18 Volume: $15.19k Tax: Buy 23% / Sell 2…
$Mekuna | #Mekuna ---------------------------------- 🚨 Alert Time (UTC): 2025-02-11 10:09:47 ---------------------------------- 🔍 Token Overview: CA: 0x10569d741f5aad0eaa84aec961fafcc5dd90eec4 CA Age: 2m0s | Pair: 2m0s Block: 10 | Tick: 7 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $32.67k MCap: $104.23k | ATH: $157.55k MC/Liq Ratio: 3.19 Volume: $21.12k Tax: Buy 2% / Sell 2% ----…
$BB | #BB ---------------------------------- 🚨 Alert Time (UTC): 2025-02-10 07:21:23 ---------------------------------- 🔍 Token Overview: CA: 0xd49e4d0590eac8912497ae18b7e31339d38c0302 CA Age: 5m36s | Pair: 2m0s Block: 10 | Tick: 5 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $31.50k MCap: $95.36k | ATH: $161.47k MC/Liq Ratio: 3.03 Volume: $22.59k Tax: Buy 10% / Sell 0% -----------…
$BLIND | #BLIND ---------------------------------- 🚨 Alert Time (UTC): 2025-02-09 21:35:23 ---------------------------------- 🔍 Token Overview: CA: 0xda1448f770878536ff480a972d994fed3daca1ce CA Age: 6m24s | Pair: 1m48s Block: 8 | Tick: 6 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $18.73k MCap: $39.20k | ATH: $57.78k MC/Liq Ratio: 2.09 Volume: $15.54k Tax: Buy 0% / Sell 0% -------…
🤝1
$USAID | #USAID ---------------------------------- 🚨 Alert Time (UTC): 2025-02-08 19:02:11 ---------------------------------- 🔍 Token Overview: CA: 0x9e242144d887a067d5bbe087d29fc78bf0e3665f CA Age: 8m24s | Pair: 2m0s Block: 10 | Tick: 5 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $39.48k MCap: $149.99k | ATH: $225.47k MC/Liq Ratio: 3.80 Volume: $26.02k Tax: Buy 10% / Sell 0% ----…
$AYA | #AYA ---------------------------------- 🚨 Alert Time (UTC): 2025-02-06 20:25:47 ---------------------------------- 🔍 Token Overview: CA: 0xd1beadfcc8b46061c5972e80e27ac4b79276ee64 CA Age: 3m0s | Pair: 1m48s Block: 9 | Tick: 9 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $18.06k MCap: $40.94k | ATH: $60.85k MC/Liq Ratio: 2.27 Volume: $22.78k Tax: Buy 23% / Sell 23% ----------…
👍1
$MIND | #MIND ---------------------------------- 🚨 Alert Time (UTC): 2025-02-06 19:51:59 ---------------------------------- 🔍 Token Overview: CA: 0x0293511d40c6a961b4ba9a5faa02d51a130559c0 CA Age: 8m24s | Pair: 2m0s Block: 10 | Tick: 7 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $41.14k MCap: $159.55k | ATH: $237.24k MC/Liq Ratio: 3.88 Volume: $26.90k Tax: Buy 20% / Sell 0% ------…
$BITPLUS | #BITPLUS ---------------------------------- 🚨 Alert Time (UTC): 2025-02-06 15:14:35 ---------------------------------- 🔍 Token Overview: CA: 0x14b5c2a86c2cbc9094dafb9ca2857657d9c5e7ac CA Age: 1m36s | Pair: 1m12s Block: 5 | Tick: 6 Contract | Owner ---------------------------------- 📊 Market Data: Liquidity: $20.52k MCap: $48.70k | ATH: $121.77k MC/Liq Ratio: 2.37 Volume: $25.91k Tax: Buy 18% / Sell 18% …
Showing the 12 most recent of 20 posts we hold for @atlantes_calls. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“🚀 Atlantes Calls 🚀” (@atlantes_calls), 1,693 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/atlantes_calls.
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.