Telegram RegisterThe public register of Telegram

Channel

Forex GDP

@GDP_official

On this record: Topic · Observations · Growth · Engagement · Posts · Cite this entry

13,275subscribers

-117 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-1003838337663
TypeChannel
Username@GDP_official
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/GDP_official

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 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.

Views per post sit far below this size band

1.5 average views per post against 13,275 subscribers — an engagement rate of 0.012%. Across the 6,344 registered channels in the same cohort — 10,002–31,609 subscribers, posting mainly in English — the middle half sit between 2.73% and 15.7%, with a median of 7.33%.

What this was computed from
Window30 days (13 July 2026 12 August 2026)
Posts measured63 of 63 published in the window (63 exact, 0 rounded by Telegram)
Views totalled97
Mature posts only0.015% over 18 posts read at least 24h after publication
Subscribers13,275 measured 12 August 2026
Cohortb10000:eng · 6,344 channels · p10 0.726% · p25 2.73% · p50 7.33% · p75 15.7% · p90 28.3%
Position in cohort0.173th percentile · 1/500 the cohort median
Uncertainty±0.217% of the figure, from Telegram’s rounding
Post languageEnglish · 100.0%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 key err_low, last confirmed 12 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.

Growth

13,27513,39213,333.57 August 2026 — 13,392 subscribers7 August 2026 — 13,392 subscribers8 August 2026 — 13,377 subscribers9 August 2026 — 13,365 subscribers10 August 2026 — 13,306 subscribers11 August 2026 — 13,287 subscribers12 August 2026 — 13,275 subscribers7 August 202612 August 2026
7 measurements spanning 5 days, net -117. 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 13,257–13,410 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:2613,275-12
11 Aug 2026, 11:2413,287-19
10 Aug 2026, 10:0213,306-59
9 Aug 2026, 07:1213,365-12
8 Aug 2026, 09:3613,377-15
7 Aug 2026, 19:1613,392no change
7 Aug 2026, 19:0413,392first reading

Engagement

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

ERR · 30 days
0.012%
avg views ÷ 13,275 subscribers
Avg views / post
1.5
63 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
63
of 63 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held63 (6 August 202612 August 2026)
Views total97
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 11:53 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.

Recent posts

12 Aug 2026, 11:46 UTC1 viewsread 12 August 2026
Photo

CPI ISN’T THE ONLY THING MOVING THE MARKET TODAY. 📊 The market is also watching U.S. Treasury yields + the fiscal picture. And right now, the U.S. 10-year yield is around 4.7%, near an 18-month high. Why Gold traders should care: 📈 Higher yields / stronger USD → can pressure Gold 📉 Falling yields / weaker USD → can support Gold 🔥 CPI surprise → can quickly change the whole rate expectation

12 Aug 2026, 11:19 UTC1 viewsread 12 August 2026
Photo

KEEP JOINING VIP 99% ACCURATE SIGNALS 30_45 SIGNALS DAILY ASK FOR THE ABOVE ADDRESS JOIN VIP AND EARN ✅✅

12 Aug 2026, 09:06 UTC2 viewsread 12 August 2026

GOLD BUY NOW ENTRY ZONE: 4407.1 – 4402.1 TP 1: 4409.1 TP 2: 4419.1 SL: 4397

12 Aug 2026, 07:51 UTC3 viewsread 12 August 2026
Photo

FULL MARGIN ACTIVE +70pips✅ Close all now or set breakeven! Don't be greedy and follow my instructions 🔥

12 Aug 2026, 06:44 UTC2 viewsread 12 August 2026
Photo

Good Morning Wednesday Every trade, every lesson, every late night studying charts. This is your work, your discipline and your growth. You’ve put in the effort, faced challenges head on and built yourself into the trader you are today. Keep pushing, keep learning and remember you are your greatest investment. Let’s conquer this day together! 🚀🔥

11 Aug 2026, 14:59 UTC2 viewsread 12 August 2026
Photo

To the moon 130pips ✅✅✅ market so volatile, so beware ok

11 Aug 2026, 14:59 UTC1 viewsread 12 August 2026
Photo

Buy Gold Hit Tp1! Running +60pips! 🫵🏻🔥 Close half set breakeven guys! Zero risk for today

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

“Forex GDP” (@GDP_official), 13,275 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/GDP_official.

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.