Telegram RegisterThe public register of Telegram
Telegram profile photo for GOLD BUG · Gold Ratio trading

Channel

GOLD BUG · Gold Ratio trading

@goldbug_gold

On this record: Growth · Engagement · Posts · Citations · Cite this entry

5subscribers

+0 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-1004370892774
TypeChannel
Username@goldbug_gold
Created1 August 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live16 September 2026
Measurements held4
Confirmed unchanged4 times, most recently 16 September 2026
On Telegramt.me/goldbug_gold

Growth

565.57 August 2026 — 5 subscribers13 August 2026 — 5 subscribers15 August 2026 — 6 subscribers23 August 2026 — 5 subscribers7 August 202623 August 2026
4 measurements spanning 17 days. 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 5–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 16:235-1
15 Aug 2026, 03:126+1
13 Aug 2026, 00:335no change
7 Aug 2026, 03:025first reading

Engagement

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

Recent posts

7 Aug 2026, 15:37 UTC5 viewsread 13 August 2026
Photo

Why investors have followed the Gold/Silver Ratio for decades Gold and silver have long been viewed side by side. Both are used as stores of value, but they can behave very differently in the market. That makes one question especially useful: how is gold performing relative to silver? The Gold/Silver Ratio (GSR) answers it by showing the price of gold measured in silver. Say gold rises 5% and silver rises 15%. Bot

4 Aug 2026, 14:10 UTC8 viewsread 13 August 2026
Photo

How a GOLD BUG trade goes through Graphene DEX GOLD BUG doesn't keep trades in an application database. You make a prediction on the Gold/Silver Ratio and open a position on the ratio moving up or down. Here's what happens next: • the position is created through Graphene DEX; • execution happens on-chain, not on the application's server; • network fees are paid in GPH; • profit and loss are settled in GOLD, not U

3 Aug 2026, 18:19 UTC8 viewsread 13 August 2026
Photo

Why not dollars? In GOLD BUG, you don't predict the price of gold in USD. Instead, you predict how gold moves relative to silver. Open a position on the Gold/Silver Ratio going ▲ up or ▼ down. • P/L is measured in gold, not dollars. • Trades are executed through the Graphene DEX. 🧪 Soft launch: TEST GOLD only, not real money. Try opening your first position, then tell us what was confusing or unclear. Your feed

3 Aug 2026, 17:23 UTC8 viewsread 13 August 2026
Photo

GOLD BUG · soft launch What it is • A prediction on the price of gold measured in silver (gold/silver pair) • You open a position on the pair going up or down • P/L is measured in gold, not dollars • All trades go through the Graphene DEX (fees in GPH) Where we are now • TEST GOLD: test assets, not real money • Positions are already written on-chain • This stage is about product feedback, not hype How to start 1.

Showing the 5 most recent of 5 posts we hold for @goldbug_gold. 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 2 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.

Named by

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“GOLD BUG · Gold Ratio trading” (@goldbug_gold), 5 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/goldbug_gold.

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.