Telegram RegisterThe public register of Telegram
Telegram profile photo for RAVEN SIGNALS PRO 🦅 TM

Channel

RAVEN SIGNALS PRO 🦅 TM

@raventradingsignals

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

50subscribers

-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-1003565411033
TypeChannel
Username@raventradingsignals
CreatedBetween 1 December 2025 and 10 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/raventradingsignals

Growth

5052517 August 2026 — 52 subscribers10 August 2026 — 52 subscribers16 August 2026 — 50 subscribers7 August 202616 August 2026
3 measurements spanning 9 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 50–52 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 08:2750-2
10 Aug 2026, 10:1552no change
7 Aug 2026, 15:2752first reading

Engagement

19 posts held, back to 10 April 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 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 14 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
6s
Average length
6s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

14 Apr 2026, 11:04 UTC3 viewsread 10 August 2026
Photo

ᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴ᅠ

14 Apr 2026, 11:04 UTC4 viewsread 10 August 2026
Forwarded from @kingforexxsVideo

We are about to send out investment profits to all our investors. We have a lot of investors, we cannot post all investment payout proofs here, we will post a few. Congratulations to all our investors 🎉🎉 ✅✔️💯

14 Apr 2026, 11:04 UTC3 viewsread 10 August 2026

Inform me when you receive the paymentᅠ ￴￴￴￴ᅠ ￴￴￴￴ᅠ ￴￴￴￴ᅠ ￴￴￴￴ᅠ ￴￴￴￴ᅠ ￴￴￴￴

14 Apr 2026, 11:04 UTC2 viewsread 10 August 2026

As this is important to meᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴ᅠ

14 Apr 2026, 11:04 UTC2 viewsread 10 August 2026

I hope you’re doing well I’m reaching out because I’m ready to proceed with an investment

14 Apr 2026, 11:04 UTC2 viewsread 10 August 2026

I’ve taken time to understand how the system works and I’m fully prepared to follow all instructions carefully to ensure a smooth process

10 Apr 2026, 16:43 UTC2 viewsread 10 August 2026
Forwarded from @kingforexxs

Always remember to set your breakeven if you're holding

10 Apr 2026, 16:43 UTC2 viewsread 10 August 2026
Forwarded from @kingforexxsPhoto

Gold buy finally has already smashed my TP1! Gold Buy Hit Tp1 - running 113pips What are you waiting for? Go collect those profits! Congrats everyone who hold until hit tp1!

10 Apr 2026, 16:43 UTC2 viewsread 10 August 2026
Forwarded from @kingforexxs

Gold buy 4773.5 - 4768.5 Sl : 4763.5 tp1 : 4780.5 tp2 : 4790.5

10 Apr 2026, 16:43 UTC2 viewsread 10 August 2026
Forwarded from @kingforexxsPhoto

Zerofloat buy gold - 60pips running

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“RAVEN SIGNALS PRO 🦅 TM” (@raventradingsignals), 50 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/raventradingsignals.

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.