Telegram RegisterThe public register of Telegram
Telegram profile photo for FXPesa

Channel

FXPesa

@fxpesatelegram

Verified by Telegram

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Cite this entry

11,988subscribers

-247 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001199319360
TypeChannel
Username@fxpesatelegram
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 November 2026
Measurements held59
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/fxpesatelegram

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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 word for word on 1 other registered channel. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@blueberrymarketsofficial/307336 Aug 2026, 06:41 UTC@fxpesatelegram/11566 · this entry6 Aug 2026, 06:50 UTC1.009 minutes
@blueberrymarketsofficial/307386 Aug 2026, 11:39 UTC@fxpesatelegram/11570 · this entry6 Aug 2026, 11:49 UTC1.0010 minutes
@blueberrymarketsofficial/307487 Aug 2026, 09:34 UTC@fxpesatelegram/11575 · this entry7 Aug 2026, 09:34 UTC1.00under a minute
@blueberrymarketsofficial/307497 Aug 2026, 10:24 UTC@fxpesatelegram/11576 · this entry7 Aug 2026, 10:28 UTC1.004 minutes
@blueberrymarketsofficial/307467 Aug 2026, 07:38 UTC@fxpesatelegram/11572 · this entry7 Aug 2026, 07:42 UTC0.934 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@blueberrymarketsofficial5 (5/5 hand-verifiable sample passed)0.994 minutes@blueberrymarketsofficial (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. 5 of the 5 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 19 comparable posts for this entry, running 4 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 2, the earliest publisher we hold is @blueberrymarketsofficial. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 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 1 other registered channel, 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

11,98812,23512,111.57 August 2026 — 12,235 subscribers7 August 2026 — 12,235 subscribers7 August 2026 — 12,232 subscribers9 August 2026 — 12,228 subscribers10 August 2026 — 12,222 subscribers10 August 2026 — 12,213 subscribers11 August 2026 — 12,211 subscribers12 August 2026 — 12,203 subscribers16 August 2026 — 12,198 subscribers17 August 2026 — 12,197 subscribers18 August 2026 — 12,202 subscribers19 August 2026 — 12,201 subscribers20 August 2026 — 12,195 subscribers21 August 2026 — 12,192 subscribers22 August 2026 — 12,187 subscribers24 August 2026 — 12,171 subscribers25 August 2026 — 12,169 subscribers26 August 2026 — 12,170 subscribers27 August 2026 — 12,171 subscribers28 August 2026 — 12,172 subscribers29 August 2026 — 12,176 subscribers30 August 2026 — 12,177 subscribers31 August 2026 — 12,168 subscribers1 September 2026 — 12,176 subscribers2 September 2026 — 12,175 subscribers3 September 2026 — 12,181 subscribers5 September 2026 — 12,174 subscribers8 September 2026 — 12,166 subscribers11 September 2026 — 12,173 subscribers13 September 2026 — 12,163 subscribers14 September 2026 — 12,173 subscribers16 September 2026 — 12,163 subscribers19 September 2026 — 12,170 subscribers25 September 2026 — 12,156 subscribers4 October 2026 — 12,122 subscribers8 October 2026 — 12,116 subscribers13 October 2026 — 12,099 subscribers14 October 2026 — 12,094 subscribers15 October 2026 — 12,082 subscribers16 October 2026 — 12,081 subscribers17 October 2026 — 12,079 subscribers18 October 2026 — 12,073 subscribers19 October 2026 — 12,071 subscribers20 October 2026 — 12,064 subscribers21 October 2026 — 12,057 subscribers22 October 2026 — 12,044 subscribers23 October 2026 — 12,035 subscribers24 October 2026 — 12,034 subscribers25 October 2026 — 12,033 subscribers26 October 2026 — 12,039 subscribers27 October 2026 — 12,037 subscribers28 October 2026 — 12,039 subscribers29 October 2026 — 12,031 subscribers31 October 2026 — 12,024 subscribers1 November 2026 — 12,018 subscribers2 November 2026 — 12,019 subscribers3 November 2026 — 12,009 subscribers4 November 2026 — 11,997 subscribers5 November 2026 — 11,988 subscribers7 August 20265 November 2026
59 measurements spanning 90 days, net -247. 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 11,951–12,272 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 59
Measured (UTC)SubscribersChange
5 Nov 2026, 19:2111,988-9
4 Nov 2026, 17:2511,997-12
3 Nov 2026, 18:5912,009-10
2 Nov 2026, 20:1612,019+1
1 Nov 2026, 21:1112,018-6
31 Oct 2026, 19:5012,024-7
29 Oct 2026, 17:3512,031-8
28 Oct 2026, 20:1112,039+2
27 Oct 2026, 20:4512,037-2
26 Oct 2026, 18:3112,039+6
25 Oct 2026, 20:5712,033-1
24 Oct 2026, 21:2712,034-1
23 Oct 2026, 21:2512,035-9
22 Oct 2026, 19:4712,044-13
21 Oct 2026, 13:5612,057-7
20 Oct 2026, 11:4712,064-7
19 Oct 2026, 12:2812,071-2
18 Oct 2026, 15:1612,073-6
17 Oct 2026, 16:2812,079-2
16 Oct 2026, 16:3712,081first reading

Engagement

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

ERR · 30 days
4.39%
avg views ÷ 11,988 subscribers
Avg views / post
527
35 posts measured
Reaction rate
0.425%
reactions ÷ views · ER floor
Posts in window
35
of 131 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 26 of 35 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 5 November 2026
Posts held131 (4 August 2026 – 5 November 2026)
Views total18,435
Reactions total60
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 19:21 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

Video runtime
1m 49s
Average length
55s

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

152 reactions across 76 posts, in 7 distinct kinds. The most used accounts for 68.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤10468.4%
🔥3523.0%
👍42.63%
😢31.97%
🥰31.97%
👏21.32%
👎10.658%

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

Measured over the 131 most recent posts we hold, published 4 August 2026 to 5 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 35 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).

5 Nov 2026, 08:20 UTC286 views1 reactionsread 5 November 2026

📈 [Buy Limit] GBPUSD - Bullish - We look to Buy at 1.3451 ▪ Our short term bias remains positive. ▪ Intraday dips continue to attract buyers and there is no clear indication that this sequence for trading is coming to an end. ▪ 20 4hour EMA is at 1.3447. ▪ We look for a temporary move lower. ▪ Risk/reward is ample to call a buy trade. Confidence: ⭐⭐⭐ ⛔ Stop: 1.3399 🎯 Target 1: 1.3599 🎯 Target 2: 1.3629 ⌛ Expires: 2…

🔥1

5 Nov 2026, 07:37 UTC305 viewsread 5 November 2026

📈 [Buy Limit] USDJPY - Bullish - We look to Buy at 157.90 ▪ We are trading at oversold extremes. ▪ A Doji style candle has been posted from the base. ▪ This is positive for sentiment and the uptrend has potential to return. ▪ Preferred trade is to buy on dips. ▪ Bespoke support is located at 157.90. Confidence: ⭐⭐⭐ ⛔ Stop: 157.42 🎯 Target 1: 159.27 🎯 Target 2: 160.55 ⌛ Expires: 2026-11-06 06:00 (GMT+00:00) Market C…

5 Nov 2026, 06:58 UTC307 viewsread 5 November 2026

📈 [Buy Limit] EURUSD - Bullish - We look to Buy at 1.1230 ▪ There is no clear indication that the upward move is coming to an end. ▪ Although we remain bullish overall, a correction is possible with plenty of room to move lower without impacting the trend higher. ▪ Risk/Reward would be poor to call a buy from current levels. ▪ A move through 1.1270 will confirm the bullish momentum. ▪ The measured move target is 1.1…

5 Nov 2026, 06:39 UTC313 viewsread 5 November 2026

📉 [Sell Limit] Gold - Bearish - We look to Sell at 4194 ▪ Broken out of the wedge formation to the upside. ▪ The measured move target is 4082. ▪ We are trading at overbought extremes. ▪ Bespoke resistance is located at 4194. ▪ Preferred trade is to sell into rallies. ▪ Although the anticipated move lower is corrective, it does offer ample risk/reward today. Confidence: ⭐⭐⭐ ⛔ Stop: 4244 🎯 Target 1: 4049 🎯 Target 2: …

4 Nov 2026, 13:39 UTC468 views1 reactionsread 5 November 2026

🇺🇸 US Midterms: What changed for the markets? Democrats have taken control of both chambers of Congress, and markets are already reacting. 🟡 Gold is up 💵 The dollar is weaker 📉 Treasury yields have eased But the bigger question is: does the election actually change the market outlook, or just the political backdrop? Rufas Kamau unpacks what this could mean for Gold, DXY, US indices and Oil. 👉 Read the full analy…

🔥1

4 Nov 2026, 08:02 UTC493 views2 reactionsread 5 November 2026

📈 [Buy Limit] GBPUSD - Bullish - We look to Buy at 1.3431 ▪ Our short term bias remains positive. ▪ There is no clear indication that the upward move is coming to an end. ▪ 50 1hour EMA is at 1.3420. ▪ We look for a temporary move lower. ▪ Risk/Reward would be poor to call a buy from current levels. Confidence: ⭐⭐⭐ ⛔ Stop: 1.3381 🎯 Target 1: 1.3581 🎯 Target 2: 1.3601 ⌛ Expires: 2026-11-05 06:00 (GMT+00:00) Market C…

❤1🔥1

4 Nov 2026, 07:37 UTC452 views2 reactionsread 5 November 2026

📉 [Sell Limit] USDJPY - Bearish - We look to Sell at 158.95 ▪ Buying pressure from 157.38 resulted in prices rejecting the dip. ▪ The current move higher is expected to continue. ▪ Although the bulls are in control, the stalling positive momentum indicates a turnaround is possible. ▪ This is negative for short term sentiment and we look to set shorts at good risk/reward levels for a further correction lower. ▪ We th…

🔥2

4 Nov 2026, 07:18 UTC428 views1 reactionsread 5 November 2026

📈 [Buy Limit] EURUSD - Bullish - We look to Buy at 1.1210 ▪ There is no clear indication that the upward move is coming to an end. ▪ Although we remain bullish overall, a correction is possible with plenty of room to move lower without impacting the trend higher. ▪ Risk/Reward would be poor to call a buy from current levels. ▪ A move through 1.1250 will confirm the bullish momentum. ▪ The measured move target is 1.1…

🔥1

4 Nov 2026, 06:39 UTC389 views3 reactionsread 5 November 2026

📉 [Sell Limit] Gold - Bearish - We look to Sell at 4032 ▪ Broken out of the wedge formation to the upside. ▪ Inside Soldiers have been posted on the daily chart. ▪ The conflicting views have resulted in the immediate outlook being hard to interpret. ▪ Bespoke resistance is located at 4032. ▪ Preferred trade is to sell into rallies. Confidence: ⭐⭐⭐ ⛔ Stop: 4082 🎯 Target 1: 3875 🎯 Target 2: 3768 ⌛ Expires: 2026-11-05…

❤1🔥1😢1

4 Nov 2026, 06:26 UTC390 views2 reactionsread 5 November 2026
Photo

Traders, the poll results are in! 👀📊 In our first poll, 94% of responses indicated that financial pressure has, at least sometimes, influenced the urge to trade. And when we asked what you'd do after two consecutive losses while feeling frustrated, 47% chose to step away and reset. Interesting, right? Knowing when to trade is important, but knowing when to step away matters too. Join us on 10 November at 8 PM EAT…

🔥2

3 Nov 2026, 08:12 UTC502 views2 reactionsread 5 November 2026

📉 [Sell Limit] GBPUSD - Bearish - We look to Sell at 1.3442 ▪ Daily signals are mildly bearish. ▪ Preferred trade is to sell into rallies. ▪ Rallies should be capped by yesterday's high. ▪ Risk/reward is ample to call a sell trade. ▪ Bespoke resistance is located at 1.3450. Confidence: ⭐⭐⭐ ⛔ Stop: 1.3485 🎯 Target 1: 1.3313 🎯 Target 2: 1.3293 ⌛ Expires: 2026-11-04 06:00 (GMT+00:00) Market Chart

❤1🔥1

3 Nov 2026, 07:47 UTC498 viewsread 5 November 2026
Poll

You've taken two losses today. Another potential setup appears, but you're feeling frustrated.What's your next move?

  1. Take the trade if it meets my plan24%
  2. Step away and reset55%
  3. Reduce my position size and reassess24%
  4. Keep trading to recover my losses Copy poll10%

The shares total 113%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

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

Polls

The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

3 Nov 2026, 07:47 UTCAnonymous Poll51 voters

You've taken two losses today. Another potential setup appears, but you're feeling frustrated.What's your next move?

  1. Take the trade if it meets my plan24%
  2. Step away and reset55%
  3. Reduce my position size and reassess24%
  4. Keep trading to recover my losses Copy poll10%

The shares total 113%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

2 Nov 2026, 07:39 UTCAnonymous Poll31 voters

Have you ever felt pressured to enter a trade because you needed to make money?

  1. Yes, I've been there 😅52%
  2. Sometimes, especially after a loss55%
  3. No, I stick to my trading plan6%

The shares total 113%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

6 Aug 2026, 09:18 UTCAnonymous Poll63 voters

What’s most likely to make a trader abandon their plan?

  1. FOMO35%
  2. Greed after a winning trade25%
  3. Social media pressure16%
  4. Trying to recover a loss63%

The shares total 139%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 131 most recent posts we hold, published 4 August 2026 to 5 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“FXPesa” (@fxpesatelegram), 11,988 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/fxpesatelegram.

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.