Telegram RegisterThe public register of Telegram
Telegram profile photo for 46 FX

Channel

46 FX

@fourtysixfx1

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry

239subscribers

-18 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-1001322709870
TypeChannel
Username@fourtysixfx1
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/fourtysixfx1

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 23 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 2 other registered channels. This entry also sits inside a group of 3 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
@BearBullGoldFree1/121821 Aug 2025, 13:08 UTC@fourtysixfx1/8105 · this entry1 Aug 2025, 13:09 UTC1.002 minutes
@BearBullGoldFree1/121851 Aug 2025, 15:14 UTC@fourtysixfx1/8109 · this entry1 Aug 2025, 15:56 UTC1.0043 minutes
@BearBullGoldFree1/121901 Aug 2025, 17:59 UTC@fourtysixfx1/8113 · this entry1 Aug 2025, 18:00 UTC1.0072 seconds
@BearBullGoldFree1/121932 Aug 2025, 06:15 UTC@fourtysixfx1/8115 · this entry2 Aug 2025, 06:16 UTC1.002 minutes
@BearBullGoldFree1/121952 Aug 2025, 06:17 UTC@fourtysixfx1/8117 · this entry2 Aug 2025, 06:18 UTC1.00under a minute
@FundedNextOfficialCommunity1/90251 Aug 2025, 13:08 UTC@fourtysixfx1/8105 · this entry1 Aug 2025, 13:09 UTC1.002 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
@BearBullGoldFree15 (5/5 hand-verifiable sample passed)1.002 minutes@BearBullGoldFree1 (5–0)
@FundedNextOfficialCommunity15 (5/5 hand-verifiable sample passed)1.002 minutes@FundedNextOfficialCommunity1 (5–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. None of the 10 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 5 comparable posts for this entry, running 1 August 2025 to 2 August 2025. 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 3 channels, the one whose matching posts we hold earliest is @FundedNextOfficialCommunity1. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 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 3 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

2392572487 August 2026 — 257 subscribers8 August 2026 — 257 subscribers23 August 2026 — 253 subscribers31 August 2026 — 252 subscribers10 September 2026 — 249 subscribers6 October 2026 — 247 subscribers14 October 2026 — 246 subscribers20 October 2026 — 244 subscribers27 October 2026 — 243 subscribers3 November 2026 — 241 subscribers11 November 2026 — 239 subscribers7 August 202611 November 2026
11 measurements spanning 96 days, net -18. 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 236–260 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Nov 2026, 09:16239-2
3 Nov 2026, 15:30241-2
27 Oct 2026, 05:46243-1
20 Oct 2026, 17:42244-2
14 Oct 2026, 04:00246-1
6 Oct 2026, 01:41247-2
10 Sept 2026, 13:40249-3
31 Aug 2026, 10:36252-1
23 Aug 2026, 14:46253-4
8 Aug 2026, 09:16257no change
7 Aug 2026, 10:31257first reading

Engagement

18 posts held, back to 1 August 2025 — the 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 18 posts for this entry, the most recent from 2 August 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Aug 2025, 06:18 UTC42 viewsread 8 August 2026

(TRADING BASE SCHEME) For our subscribers who maybe too occupied and cannot follow the signals every time, This package works perfectly for busy traders, beginners or anyone who doesn't want to take risks while trading personally.. Each Investors capital is added to our official trading portfolio and traded to yield profits. 1 : Deposit $500 I will return $350 every Friday night. 2 : Deposit $1000 I will return $7…

2 Aug 2025, 06:16 UTC33 viewsread 8 August 2026
Photo

We are done sending Todays payout on BTC to all Trading Base Scheme investors ✅💯 Thank you all for trusting us 💯 If you’re interested Contact: @Robertfinleyfx congratulations👏💯

1 Aug 2025, 18:00 UTC24 viewsread 8 August 2026
Photo

We are done sending USDT todays payout to all Trading Base Scheme investors ✅💯 Thank you all for trusting us 💯 If you’re interested Contact: @Robertfinleyfx congratulations 👏

1 Aug 2025, 15:56 UTC15 viewsread 8 August 2026

💎Todays payout has just kicked off🤩 Trading Base Scheme members should confirm the usdt trc20 address we registered them with so we can send your weekly payout ! Contact: @Robertfinleyfx if interested to join the program ! 👍👍

1 Aug 2025, 13:09 UTC12 viewsread 8 August 2026

‼️Important announcement‼️ Congratulations🥂 For all candidate who invested in the last Trading Base Scheme INVESTMENT .. your profits are all Ready..we will be sending it out in few minutes now✅ Contact Admin 👉 @Robertfinleyfx

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

“46 FX” (@fourtysixfx1), 239 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/fourtysixfx1.

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.