Telegram RegisterThe public register of Telegram
Telegram profile photo for SignalProvider (Free Forex Trading Signals)

Channel

SignalProvider (Free Forex Trading Signals)

@signalsproviderfx_0

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

79,015subscribers

+17,211 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1003792184893
TypeChannel
Username@signalsproviderfx_0
Description𝗔𝗰𝗰𝗼𝘂𝗻𝘁 Investment S𝗲𝗿𝘃𝗶𝗰𝗲* S𝗮𝘃𝗲 Y𝗼𝘂𝗿 E𝗾𝘂𝗶𝘁𝘆 #𝗥𝗲𝗰𝗼𝘃𝗲𝗿Y𝗼𝘂𝗿L𝗼𝘀𝘀 #𝗠𝗮𝗸𝗲Y𝗼𝘂rC𝗮𝗽𝗶𝘁𝗮𝗹S𝗮𝗳𝗲 #𝗚𝗲𝘁C𝗼𝗻𝗳𝗶𝗿𝗺𝗗𝗮𝗶𝗹𝘆P𝗿𝗼𝗳𝗶𝘁. #FreeDailySignals #VipService #11YearsTradingExperiencee @RealAdmin_001
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/signalsproviderfx_0

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 10 other registered channels. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@GOLDMASTEROFTRADE_0/844420 Aug 2026, 16:58 UTC@signalsproviderfx_0/11636 · this entry20 Aug 2026, 17:04 UTC1.006 minutes
@GOLDMASTEROFTRADE_0/878326 Aug 2026, 00:59 UTC@signalsproviderfx_0/11970 · this entry26 Aug 2026, 00:59 UTC1.00under a minute
@GOLDMASTEROFTRADE_0/909529 Aug 2026, 12:51 UTC@signalsproviderfx_0/12280 · this entry29 Aug 2026, 12:56 UTC1.005 minutes
@signalsproviderfx_0/14487 · this entry27 Sept 2026, 16:16 UTC@GOLDMASTEROFTRADE_0/1131627 Sept 2026, 16:16 UTC1.00under a minute
@signalsproviderfx_0/14972 · this entry3 Oct 2026, 12:58 UTC@GOLDMASTEROFTRADE_0/117983 Oct 2026, 12:58 UTC1.00under a minute
@GOLDMASTEROFTRADE_0/138426 Nov 2026, 20:30 UTC@signalsproviderfx_0/17009 · this entry6 Nov 2026, 20:34 UTC1.004 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@GOLDMASTEROFTRADE_042 (7/8 hand-verifiable sample passed)1.00under a minute@GOLDMASTEROFTRADE_0 (35–7)
@goldsclaper10o32 (7/8 hand-verifiable sample passed)1.00under a minute@goldsclaper10o (25–7)
@GolddExpert_030 (6/8 hand-verifiable sample passed)1.00under a minutethis entry (17–13)
@Gold_Forex_Institute24 (8/8 hand-verifiable sample passed)1.002 minutes@Gold_Forex_Institute (19–5)
@Goldscalpingsignalls19 (8/8 hand-verifiable sample passed)1.0072 seconds@Goldscalpingsignalls (15–4)
@goldenfx_3319 (8/8 hand-verifiable sample passed)1.001.6 hoursthis entry (18–1)
@itradeforex_withworld13 (8/8 hand-verifiable sample passed)0.985 minutes@itradeforex_withworld (10–3)
@TheKingOfForexProo13 (7/8 hand-verifiable sample passed)1.0014 minutes@TheKingOfForexProo (8–5)
@MichaelGoldFx_0011 (8/8 hand-verifiable sample passed)1.005 minutes@MichaelGoldFx_00 (8–3)
@Gold_Forex_Institute0010 (8/8 hand-verifiable sample passed)1.005 minuteseven

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 172 of the 172 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 470 comparable posts for this entry, running 6 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 4 channels, the one whose matching posts we hold earliest is @signalsproviderfx_0 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

47,64879,01563,331.57 August 202615 November 2026
66 measurements spanning 101 days, net +17,211. 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 42,943–83,720 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
15 Nov 2026, 22:1679,015+17,148
12 Nov 2026, 09:0661,867-1,989
10 Nov 2026, 07:3763,856+3,477
8 Nov 2026, 19:4660,379+6,959
7 Nov 2026, 11:0753,420+1,995
6 Nov 2026, 13:0951,425+947
5 Nov 2026, 12:4650,478+395
4 Nov 2026, 15:3650,083-235
3 Nov 2026, 18:1750,318+1,899
2 Nov 2026, 18:4448,419-241
1 Nov 2026, 16:3048,660-764
31 Oct 2026, 14:0049,424-856
30 Oct 2026, 14:0650,280-1,414
29 Oct 2026, 13:4851,694-858
28 Oct 2026, 09:4152,552-696
27 Oct 2026, 08:1653,248-650
26 Oct 2026, 11:0453,898-1,069
25 Oct 2026, 11:5754,967-367
24 Oct 2026, 13:4655,334-850
23 Oct 2026, 14:3756,184first reading

Engagement

2,507 posts held, back to 6 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 207 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.186%
avg views ÷ 79,015 subscribers
Avg views / post
147
775 posts measured
Reaction rate
0.562%
reactions ÷ views · ER floor
Posts in window
775
of 2,507 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 37 of 775 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held2,507 (6 August 2026 – 17 November 2026)
Views total114,193
Reactions total27
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 12:10 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈7,640
Videos
≈85
Links
≈3,530

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
3m 06s
Average length
16s

Measured directly from 12 videos 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.

Reaction mix

64 reactions across 37 posts, in 9 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3250.0%
👍69.38%
🔥57.81%
🤩57.81%
🎉46.25%
🥰46.25%
💯34.69%
😍34.69%
❤‍🔥23.13%

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 50 of the 1,000 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 64 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 8 October 2026 to 17 November 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

Telegram’s own ‘edited’ marker: 0 of 775 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 11:58 UTC41 viewsread 17 November 2026

since I joined. I have been getting paid so seamlessly and being treated with such fairness and respect means alot to meᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴

17 Nov 2026, 11:58 UTC69 viewsread 17 November 2026

Even though I may not have many words to express everything I feel right now, I truly want to acknowledge the amazing work of the organizationᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴

17 Nov 2026, 11:58 UTC69 viewsread 17 November 2026

Thank you for my payment which I just receivedᅠ ￴￴￴￴ᅠᅠ ￴￴￴￴

17 Nov 2026, 10:20 UTC30 viewsread 17 November 2026

Hit Risk ! Lets take it easy and wait for US Session 🇺🇸

17 Nov 2026, 09:23 UTC34 viewsread 17 November 2026
Photo

GOLD HIT OUR 1ST TP 140+PIPS! Collect more layers now and hold 1-2 layers to tp2 everyone.

17 Nov 2026, 09:14 UTC29 viewsread 17 November 2026
Photo

GOLD RUNNING NOW 80+PIPS GUYS! Collect your layers abit and hold another layers to tp1 !

Showing the 12 most recent of 2,507 posts we hold for @signalsproviderfx_0. 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

Named by 26 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 18 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“SignalProvider (Free Forex Trading Signals)” (@signalsproviderfx_0), 79,015 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/signalsproviderfx_0.

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.