Telegram RegisterThe public register of Telegram
Telegram profile photo for فارکس /سیگنال طلا

Channel

فارکس /سیگنال طلا

@bitgold987

Not marked by Telegram, checked 27 August 2026

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

123,314subscribers

-16,677 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002236123795
TypeChannel
Username@bitgold987
Descriptionمحمد نوروزی ربات پشتیبانی @Bitgoldhelp_bot 📈 ۷ سال سابقه حرفه‌ای در بازار فارکس 📊 آموزش و تحلیل تخصصی فارکس 🔗 پیج اینستاگرام: instagram.com/bit_gold98 《 همان اصالت ،در مقیاسی بزرگ تر 》
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live26 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/bitgold987

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 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 why it has no browse page of its own yet.

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 word for word on 4 other registered channels. 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
@bitgold987/8050 · this entry6 Aug 2026, 07:24 UTC@signal_fxgold/507786 Aug 2026, 07:24 UTC1.00under a minute
@bitgold987/8051 · this entry6 Aug 2026, 07:24 UTC@signal_fxgold/507796 Aug 2026, 07:24 UTC1.00under a minute
@bitgold987/8059 · this entry6 Aug 2026, 14:23 UTC@signal_fxgold/507876 Aug 2026, 14:23 UTC1.00under a minute
@bitgold987/8061 · this entry6 Aug 2026, 16:33 UTC@signal_fxgold/507896 Aug 2026, 16:33 UTC1.00under a minute
@bitgold987/8064 · this entry7 Aug 2026, 07:39 UTC@signal_fxgold/507927 Aug 2026, 07:39 UTC1.00under a minute
@bitgold987/8067 · this entry7 Aug 2026, 12:27 UTC@signal_fxgold/507957 Aug 2026, 12:27 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@signal_fxgold9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (5–4)
@bit_gold989 (8/8 hand-verifiable sample passed)1.00under a minute@bit_gold98 (6–3)
@XAUSDS8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (7–1)
@RavandSniper8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–0)

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. 10 of the 11 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 11 comparable posts for this entry, running 5 August 2026 to 7 August 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).

Across the whole group of 5, the earliest publisher we hold is @bit_gold98. That is a statement about our reading window, not a claim of authorship.

Views per post sit far below this size band

82.4 average views per post against 123,314 subscribers — an engagement rate of 0.067%. Across the 1,121 registered channels in the same cohort — 100,020–315,932 subscribers, posting mainly in Persian — the middle half sit between 1.85% and 8.83%, with a median of 4.42%.

What this was computed from
Window30 days (28 August 2026 – 27 September 2026)
Posts measured190 of 191 published in the window (190 exact, 0 rounded by Telegram)
Views totalled15,663
Mature posts only0.078% over 140 posts read at least 24h after publication
Subscribers123,314 measured 26 September 2026
Cohortb100000:fas · 1,121 channels · p10 0.72% · p25 1.85% · p50 4.42% · p75 8.83% · p90 16.9%
Position in cohort0.268th percentile · 1/67 the cohort median
Uncertainty±0.234% of the figure, from Telegram’s rounding
Post languagePersian · 98.5% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the keys clone_copy · clone_mutual · clone_source · err_low, last confirmed 27 September 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 4 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

123,314139,991131,652.57 August 2026 — 139,991 subscribers7 August 2026 — 139,991 subscribers8 August 2026 — 139,663 subscribers9 August 2026 — 139,253 subscribers10 August 2026 — 138,909 subscribers11 August 2026 — 138,462 subscribers12 August 2026 — 137,886 subscribers13 August 2026 — 137,423 subscribers14 August 2026 — 136,894 subscribers15 August 2026 — 136,414 subscribers17 August 2026 — 135,699 subscribers18 August 2026 — 135,250 subscribers19 August 2026 — 134,819 subscribers20 August 2026 — 134,445 subscribers21 August 2026 — 133,863 subscribers23 August 2026 — 133,348 subscribers24 August 2026 — 132,872 subscribers25 August 2026 — 132,529 subscribers26 August 2026 — 132,264 subscribers27 August 2026 — 131,951 subscribers28 August 2026 — 131,760 subscribers29 August 2026 — 131,390 subscribers30 August 2026 — 131,133 subscribers31 August 2026 — 130,750 subscribers1 September 2026 — 130,398 subscribers2 September 2026 — 130,105 subscribers4 September 2026 — 129,617 subscribers6 September 2026 — 128,917 subscribers9 September 2026 — 127,962 subscribers11 September 2026 — 127,293 subscribers13 September 2026 — 126,919 subscribers15 September 2026 — 126,379 subscribers17 September 2026 — 125,793 subscribers26 September 2026 — 123,314 subscribers7 August 202626 September 2026
34 measurements spanning 50 days, net -16,677. 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 120,812–142,493 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
26 Sept 2026, 10:38123,314-2,479
17 Sept 2026, 08:16125,793-586
15 Sept 2026, 07:16126,379-540
13 Sept 2026, 16:38126,919-374
11 Sept 2026, 23:19127,293-669
9 Sept 2026, 10:40127,962-955
6 Sept 2026, 06:37128,917-700
4 Sept 2026, 02:37129,617-488
2 Sept 2026, 14:58130,105-293
1 Sept 2026, 11:26130,398-352
31 Aug 2026, 12:36130,750-383
30 Aug 2026, 15:32131,133-257
29 Aug 2026, 17:56131,390-370
28 Aug 2026, 14:25131,760-191
27 Aug 2026, 16:02131,951-313
26 Aug 2026, 19:18132,264-265
25 Aug 2026, 19:08132,529-343
24 Aug 2026, 18:17132,872-476
23 Aug 2026, 03:37133,348-515
21 Aug 2026, 19:15133,863first reading

Engagement

361 posts held, back to 5 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 105 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.067%
avg views ÷ 123,314 subscribers
Avg views / post
82.4
190 posts measured
Reaction rate
0.791%
reactions ÷ views · ER floor
Posts in window
191
of 361 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 2 of 190 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 26 September 2026
Posts held361 (5 August 2026 – 26 September 2026)
Views total15,663
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Sept 2026, 21:42 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
≈3,270
Videos
≈964
Links
≈955

Lifetime counters from Telegram’s own channel header, read 26 September 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
8h 08m
Average length
11m 21s

Measured directly from 43 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

6 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 83.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👌583.3%
🐳116.7%

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

Measured over the 361 most recent posts we hold, published 5 August 2026 to 26 September 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

26 Sept 2026, 11:09 UTC13 viewsread 26 September 2026
Photo

🔥 اینا فقط چندتا از سودهاییه که اعضای BitGold برامون فرستادن... ما می‌تونیم هرچقدر از عملکرد خودمون تعریف کنیم؛ ولی وقتی خود اعضا نتیجه‌شون رو می‌فرستن، دیگه نیازی به تعریف ما نیست 😉💰 📸 ورق بزنید و نتیجه‌ها رو خودتون ببینید... اگه تا امروز فقط تماشاچی بودی، شاید وقتشه از نزدیک با مجموعه همراه بشی. 🟢 عضویت در مجموعه رایگانه کافیه به ربات پشتیبانی پیام بدی و مراحل عضویت رو انجام بدی: 🤖 @Bitgoldhelp_bot 🤖@Bitgoldhelp_…

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

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

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

سیگنال طلا فارکس
@forex_Xau1 · 1,077
#1
دوستان خان بورس در بازار های مالی❤️💚
@forexkhan · 131,789
#2
سیگنال فارکس Liveforex
@freesignal_live · 31,659
#3
Free Airdrop | ایردراپ
@Airdropfree_legit · 282
#4
سیگنال فارکس/ارزدیجیتال
@bit_gold98 · 483,994
#5
📈ترید | آکادمی YEGANEFX🥇
@iamyeganefx · 8,197
#6
سیگنال ترید | CryptoTrade
@sijnal · 80,357
#7
آموزش فارکس (bitgold)
@schoolbitgold · 3,103
#8
Ali Analysis
@ronesans33 · 450
#9
سیگنال انس جهانی Bitgold
@signal_fxgold · 156,702
#10
Orca Forex
@orca_forex · 655
#11
Moghadase.trading | سیگنال فارکس
@MoghadaseTrading · 1,029
#12
کانال تحلیل ارزدیجیتال (BItgold)
@bitgoldcrypto · 2,059
#13
BITS | ارز دیجیتال | بیتس
@BitsChannel · 16,838
#14
Zeus Analysis
@sarafi · 100,152
#15
تجارت آفرین
@tja_real · 777
#16
گلدن سیگنال / اُنس طَلا
@GoldenSignallFx · 313,242
#17
باینری آپشن فارسی
@gfaplus · 2,617
#18
GOLD SIGNAL سیگنال انس طلا
@GOLDSIGNALFXPRO · 21,997
#19
سیگنال رایگان انس جهانی
@best_forexx · 3,290
#20
راهنمای عضویت در VIP Bit_gold
@Registerbitgold · 755
#21
سیگنال رایگان 🐊Crocodile Trade
@crocodile_trade · 209,576
#22
سیگنال فارکس ARAD
@Forex_Fxarad · 1,194
#23
شکارچی طلای جهانی ( هاشمی) انس
@shekarchi_gold · 6,271
#24
سیگنال فارکس ARAD
@FOREX_FX_Signal_gold · 1,951
#25
faridhossinzade|فریدحسین زاده
@faridhossinzadeh_fx · 805
#26
سیگنال فارکس
@goldenpip · 80,580
#27
نتایج سیگنال های جادوگران فارکس💸
@shatsod · 1,438
#28
♻️صرافی هموطن♻️
@sarafi_hamvatan · 640
#29
XAUUSD GOLD PIPS
@XAUUSD_GOLD_PIPS_SIGNAL · 107,341
#30
استیکر فارسی
@Farsi_Stickers · 4,166
#31
XAUUSD EURUSD FOREX SIGNALS
@XAUUSDEURUSDSIGNALS · 31,717
#32
FREE GOLD SIGNALS (XAUUSD) ®
@gold_signal5 · 9,245
#33
نت آزاد
@Net_Aza · 7,452
#34
DΜƬ
@dmttttttttttt · 178
#35
S
@setare_2789 · 417
#36
GTA
@arwshinwrs · 62 (as read 26 August 2026)
#37
صاحبان فیوچرز|کریپتو|FuturesOwners|VIP SIGNAL
@FuturesOwners · 112,829
#38
ꔫ ᗪ𝖺𝗍𝖾 ᘜ𝗈𝖺𝗅𝗌
@datexgoals · 151
#39
404!
@maddymindd · 274 (as read 26 August 2026)
#40
-𝘽𝙚𝙖𝙪𝙩𝙞𝙛𝙪𝙡 𝙨𝙤𝙪𝙡.
@beautiful_soul_01 · 42
#41
Dj Star
@djstarsalmas · 573 (as read 26 August 2026)
#42
ME_1st
@MELLAT_1st · 273
#43
وال استریت ایران
@WSIRNEWS · 43,702
#44
Crypto Legends | ارز دیجیتال
@Crypto_Legends6 · 17,825
#45
REYMOoN🌔
@reymoonchannel · 732 (as read 26 August 2026)
#46
..
@gq_yd · 1,059
#47
Saynegin
@inegineow · 147 (as read 26 August 2026)
#48
آموزش ضمن خدمت کارکنان شهرداری ها، کارشناسان فنی و مالی و دهیاران خراسان جنوبی (مرکز علمی کاربردی شهرداری بیرجند)
@amoozesh_KhorasanSouth · 233 (as read 26 August 2026)
#49
طراحان و مدیران فضای سبز
@landscapedesignersandmanagers · 2,061
#50
Divine secrets🕯️
@ElegantSecrets · 108 (as read 26 August 2026)
#51
fₐᵢᵣy wₒᵣₗd
@fairrryyyy · 206
#52
𝘦𝘱𝘪𝘱𝘩𝘢𝘯𝘺
@ep1iphany · 467 (as read 26 August 2026)
#53

Read from Telegram’s recommendation API, most recently 26 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

وال استریت ایران
@WSIRNEWS · 43,702
Telegram ranks this channel #38 of 50 here — alongside 49 others — read 26 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“فارکس /سیگنال طلا” (@bitgold987), 123,314 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/bitgold987.

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.