Telegram RegisterThe public register of Telegram
Telegram profile photo for APPLE🍎GEMS 💎APE CALL ☎️

Channel

APPLE🍎GEMS 💎APE CALL ☎️

@Appelgemscall

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

3subscribers

+0 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-1002311924415
TypeChannel
Username@Appelgemscall
DescriptionETH,🚀BSC,🚀SOL,🚀ARB,🚀BASE,🚀SUI,🚀XRP,🚀…………… Founder/owner: @pumpwithme112 Admin: @kevin_Odysseus Admin: Join the (VIP) private group here https://t.me/+KPjDdZCWvcVlYWFk No culture calls
CreatedBetween 1 September 2024 and 1 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/Appelgemscall

Growth

37 August 2026 — 3 subscribers13 August 2026 — 3 subscribers7 August 202613 August 2026
2 measurements spanning 6 days. 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 16:473no change
7 Aug 2026, 15:043first reading

Engagement

20 posts held, back to 1 March 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 18 March 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
44
Videos
1
Links
36

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

18 Mar 2025, 21:46 UTC38 viewsread 13 August 2026
Photo

🌊 LOTUSTORM ($ZEN) – The Calm Before the Storm 🌸 📖 The Lore of LOTUSTORM ($ZEN) Long ago, in the land of Ethereal Waters, where mountains touched the sky and rivers whispered secrets, the world teetered between order and chaos. The Dreamers, seekers of wisdom and logic, clashed endlessly with the Provocateurs, masters of impulse and disruption. Their struggle threatened to break reality itself—yin and yang in et

18 Mar 2025, 21:44 UTC21 viewsread 13 August 2026
Photo

New Coin Found in Coingecko Name: PHOENIX Ticker: phx Network: ETHEREUM Contract Address: 0xfe3f988a90dea3ee537bb43ec1aca7337a15d002 Total Supply: 10000000000.0 Socials Website | Telegram | Twitter | Explorer | CoinGecko Markets Get more DEX Info || Banana | Maestro Pro | Maestro ━━━━━━━━━━━━━━━━━━

18 Mar 2025, 21:41 UTC28 viewsread 13 August 2026
Photo

Welcome to the Official Grand Theft Rex Cryptocurrency Telegram Group! 🚀 Your Gateway to GTRex 🚀 Welcome to the home of the Grand Theft Rex (GTRex) community! Here, we unite enthusiasts, investors, and innovators who are driving the future of decentralized finance with GTRex. What to Expect in this Group: • 💬 Active Discussions: Stay updated with the latest news, updates, and insights. • 🛠️ Tech Support: Have qu

18 Mar 2025, 21:39 UTC25 viewsread 13 August 2026
Photo

💬 "Let’s be real: Scar was the blueprint. Wit sharper than his claws, a voice smoother than Pride Rock sunsets, and the guts to challenge the status quo. Mufasa could never. 💥 #TeamScar #LongLiveTheKing" #mufasa 🟢 $scar ON SOLANA 🟢 Project may be the best project in the sol network. 📈 $Sca rtoken will do multi millions Waiting for them to get trending and carry out different marketing campaigns to make it. 🔥 I

7 Mar 2025, 16:42 UTC20 viewsread 13 August 2026
Photo

🚀 $PEDRO reached 111.56X after @pumpwithme112 's call 🚀 🔗 View call 📈 DV 🔍 Scan

7 Mar 2025, 15:02 UTC20 viewsread 13 August 2026
Photo

🚀 $PEDRO reached 48.42X after @pumpwithme112 's call 🚀 🔗 View call 📈 DV 🔍 Scan

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

“APPLE🍎GEMS 💎APE CALL ☎️” (@Appelgemscall), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Appelgemscall.

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.