Telegram RegisterThe public register of Telegram
Telegram profile photo for NEWTON CALLS 💎

Channel

NEWTON CALLS 💎

@CryptoNewtonCalls

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

55subscribers

-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-1001788008007
TypeChannel
Username@CryptoNewtonCalls
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live8 October 2026
Measurements held4
Confirmed unchanged2 times, most recently 8 October 2026
On Telegramt.me/CryptoNewtonCalls

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 91% 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

5557567 August 2026 — 57 subscribers10 August 2026 — 57 subscribers22 August 2026 — 56 subscribers26 September 2026 — 55 subscribers7 August 202626 September 2026
4 measurements spanning 50 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 55–57 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 12:2255-1
22 Aug 2026, 19:3956-1
10 Aug 2026, 07:0157no change
7 Aug 2026, 10:2057first reading

Engagement

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

Recent posts

26 Dec 2023, 08:43 UTC118 viewsread 10 August 2026
Photo

$SKUPE 🔥 MC :- $35K Ca: 8TaYiziz5gPP4wPtCQdGAMWaXfu5ySZEDu7EjL7xfENy Revoke Mint: https://solscan.io/tx/5Yfr1xLnW9VRDBrrctZu94Mivc4zbLkDUiGm7QqGkc41pnQfYcYk5NARwEgzPbHorHZUnxM2cEBinMhouMq2R7Qe Burn: https://solscan.io/tx/5L4KskCkGNdgegGe6iNi3CUP4W5kPgAUEcX6GyPfXZEzMT8updTrDaijh1kHMsm5NSVHup8LZhRRHpvJCDA1nD1w Twitter: https://x.com/skupe_sol?s=21 Website: https://skupe.xyz/ NFA DYOR

26 Dec 2023, 08:30 UTC99 viewsread 10 August 2026
Photo

$POGE 🚀 Mcap :- $20k CA: 4433PSXZxJs7Z44cjux5tErcT662ATbHjLcET4dbw3tQ BASED DEV 🔥 web : https://www.pogetoken.vip/ tg:- https://t.me/PogeTokenSol NFA DYOR

21 Dec 2023, 03:51 UTC102 viewsread 10 August 2026

15 K 🥶 10x From entry 🔥 What a play 💥 PERRY ON FIRE 🚀

21 Dec 2023, 03:43 UTC56 viewsread 10 August 2026

CURRENTLY @ 7K 4x 🔥🔥 THIS IS MOONING 🔥 based dev with a great community 🚀

21 Dec 2023, 03:24 UTC219 viewsread 10 August 2026

PERRY ON SOL 🚀 $Perry ~ 1.5k MC ~ Just launched Contract renounced and LP burnt Based Dev Sol Trending Started Do not miss out onboard this epic rocket!! https://www.dextools.io/app/en/solana/pair-explorer/H7bknaxRkn4u6j4xWwwR3AnETYYGy5jNGWoch8c9oE6f

20 Dec 2023, 10:00 UTC67 viewsread 10 August 2026

https://twitter.com/NFTnewton/status/1737405666271105194?t=1ocp3WBkHrMkpD1Orloi5g&s=19 RAID THIS TWEET $USDT 🔥

20 Dec 2023, 09:59 UTC71 viewsread 10 August 2026

$USDT - SOL (UPSIDE DOWN TURTLE) BASED DEV AND INSANE COMMUNITY 🔥 https://twitter.com/NFTnewton/status/1737405666271105194?t=1ocp3WBkHrMkpD1Orloi5g&s=19 Entered Mcap - $50k Currently -$80k DYOR/NFA CA: 4V9y1sAhJcm7C2Z4Rcg3wyBi9acjxSbcWPaBPcZEi4Xt t.me/upsideturtle twitter.com/upsideturtlesol dexscreener.com/solana/4V9y1sAhJcm7C2Z4Rcg3wyBi9acjxSbcWPaBPcZEi4Xt

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

“NEWTON CALLS 💎” (@CryptoNewtonCalls), 55 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/CryptoNewtonCalls.

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.