Telegram RegisterThe public register of Telegram
Telegram profile photo for PipsProtege📈

Channel

PipsProtege📈

@pipsprotege

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

929subscribers

-151 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-1002115203891
TypeChannel
Username@pipsprotege
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/pipsprotege

Growth

9291,0891,0097 August 2026 — 1,080 subscribers8 August 2026 — 1,080 subscribers11 August 2026 — 1,072 subscribers14 August 2026 — 1,075 subscribers17 August 2026 — 1,056 subscribers20 August 2026 — 1,033 subscribers24 August 2026 — 1,065 subscribers28 August 2026 — 1,032 subscribers31 August 2026 — 1,089 subscribers3 September 2026 — 984 subscribers11 September 2026 — 987 subscribers18 September 2026 — 929 subscribers7 August 202618 September 2026
12 measurements spanning 42 days, net -151. 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 905–1,113 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 19:17929-58
11 Sept 2026, 07:57987+3
3 Sept 2026, 12:21984-105
31 Aug 2026, 10:351,089+57
28 Aug 2026, 01:081,032-33
24 Aug 2026, 20:361,065+32
20 Aug 2026, 21:371,033-23
17 Aug 2026, 11:471,056-19
14 Aug 2026, 01:051,075+3
11 Aug 2026, 02:511,072-8
8 Aug 2026, 00:061,080no change
7 Aug 2026, 13:331,080first reading

Engagement

17 posts held, back to 13 July 2026the 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 17 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

58 reactions across 13 posts, in 3 distinct kinds. The most used accounts for 87.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5187.9%
🔥610.3%
11.72%

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 13 of the 17 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 58 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 13 July 2026 to 27 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

27 Jul 2026, 13:36 UTC126 views3 reactionsread 8 August 2026
Photo

-2R Am done for the month at this point Price is most likely bearish We will continue next month

3

Signed Elisha I

27 Jul 2026, 12:36 UTC111 viewsread 8 August 2026
Photo

Got stopped out but I am giving it one last shot

Signed Elisha I

22 Jul 2026, 13:31 UTC154 views3 reactionsread 8 August 2026
Photo

The draw on liquidity is good Had no idea why price decided to stoped us out We will make it back notwithstanding

3

Signed Elisha I

22 Jul 2026, 12:53 UTC124 views1 reactionsread 8 August 2026
Photo

Photo, posted without a caption

1

Signed Elisha I

22 Jul 2026, 12:48 UTC123 views1 reactionsread 8 August 2026
Photo

My trading view ain’t loading

1

Signed Elisha I

22 Jul 2026, 12:11 UTC136 views5 reactionsread 8 August 2026
Photo

Let’s Scalp Will be executing once price retraces

5

Signed Elisha I

16 Jul 2026, 13:19 UTC177 views10 reactionsread 8 August 2026

Our patience about to be rewarded soon Giving up is never an option to us

7🔥3

Signed Elisha I

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

“PipsProtege📈” (@pipsprotege), 929 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/pipsprotege.

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.