Telegram RegisterThe public register of Telegram
Telegram profile photo for Apache Scalp

Channel

Apache Scalp

@apache_scalp

On this record: Growth · Engagement · Posts · Cite this entry

243subscribers

+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-1001443640553
TypeChannel
Username@apache_scalp
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/apache_scalp

Growth

242243242.57 August 2026 — 243 subscribers8 August 2026 — 243 subscribers14 August 2026 — 242 subscribers22 August 2026 — 243 subscribers7 August 202622 August 2026
4 measurements spanning 15 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 242–243 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 14:18243+1
14 Aug 2026, 21:44242-1
8 Aug 2026, 09:47243no change
7 Aug 2026, 09:58243first reading

Engagement

19 posts held, back to 15 April 2024the 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 19 posts for this entry, the most recent from 19 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

19 Jun 2026, 11:38 UTC119 viewsread 8 August 2026

Fixed a bug with multiple entry into a position when a “Monitoring” tag was added to the coin, as was the case today with the ACT coin.

9 Dec 2025, 11:54 UTC376 viewsread 8 August 2026
Photo

Break All Time High for profit in the bot! Online stats.

21 Sept 2025, 12:56 UTC354 viewsread 8 August 2026
Photo

Today, we have already managed to recover more than half of the major drop in TWTUSDT.

14 Jun 2025, 19:16 UTC505 viewsread 8 August 2026
Photo

Back in profit zone after huge drop. Hopefully now the bot can show a good result!

28 May 2025, 07:11 UTC734 viewsread 8 August 2026
Photo

Got over $1000 profit in bot in less than a month. The stats are here: https://tradermake.money/trader/7NZYjZ

1 Apr 2025, 12:05 UTC749 viewsread 8 August 2026
Photo

It was the biggest loss, almost 90% (due to 2x leverage) on the ACTUSDT pair.

18 Feb 2025, 11:31 UTC764 viewsread 8 August 2026
Photo

Wow! 😢 It was a record for a drop in a single trade. We've been let down by the BAN token. And it was not an error, the bot worked strictly according to the logic. The loss could be reduced if there was first leverage, but I have 2x leverage enabled. I don't know how to avoid such trades in bot yet, I'll think about it. 🤷

Showing the 12 most recent of 19 posts we hold for @apache_scalp. 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.

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 22 August 2026 — this entry's latest reading, not the date you are reading this.

“Apache Scalp” (@apache_scalp), 243 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/apache_scalp.

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.