Channel
@GeoMarketJournal
On this record: Growth · Engagement · Posts · Citations · Cite this entry
21subscribers
+4 since we began measuring on 18 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004483907305 |
|---|---|
| Type | Channel |
| Username | @GeoMarketJournal |
| Created | Between 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 October 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 30 October 2026 |
| On Telegram | t.me/GeoMarketJournal |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Oct 2026, 14:56 | 21 | +2 |
| 18 Oct 2026, 15:45 | 19 | +2 |
| 18 Oct 2026, 08:22 | 17 | no change |
| 18 Oct 2026, 07:47 | 17 | first reading |
20 posts held, back to 12 October 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 1 page of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 18 October 2026 |
|---|---|
| Posts held | 20 (12 October 2026 – 18 October 2026) |
| Views total | 239 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Oct 2026, 08:22 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.
WEEKLY MACRO BRIEF: GEOPOLITICAL RISK PREMIUM, SAFETY FLOWS & TOKENIZATION THEMES • Canada: CFB Wainwright explosion/fire caused multiple fatalities, mass-casualty response. • Gulf: UKMTO reported a tugboat hit by projectiles near Khor Fakkan, UAE. • Yemen/Saudi: repeated Houthi drone/missile claims, interceptions, and cross-border air-defense activity. • Saudi Arabia: helicopter crash in Najran killed two officers;…
KEY HEADLINES SUMMARY - Canada: CFB Wainwright fire/explosion reportedly caused multiple fatalities; mass-casualty response underway. - Gulf security: UKMTO reported a tugboat struck by 2 projectiles northeast of Khor Fakkan, UAE. - Yemen/Saudi: Multiple Houthi drone/missile claims and Saudi intercepts; alerts in Abha/Khamis Mushait later lifted. - Saudi aviation incident: AH-6i helicopter crashed in Najran due to te…
Key Headlines Summary - Ukraine/Starlink: Axios reports SpaceX says Starlink throttling is a technical issue; Kyiv suspects political pressure. - Middle East: Houthis claim downing a Saudi AH-64 Apache near Najran; UAE reportedly weighing renewed support for Saudi operations in Yemen. - France: Riots intensified in Paris and other cities; reports of looting, metro disruption, and clashes near government sites. - Roma…
Key Headlines Summary - Zelenskyy says Starlink restrictions are impairing Ukraine’s drone interceptors and logistics; alleges deliberate operational limits. - Trump reportedly waives/loosens Russia-related sanctions and tariffs, deepening geopolitical friction. - Iran says a tanker caught fire after hitting a naval mine in the Strait of Hormuz. - Saudi/Yemen front remains active: alerts, missile launches, air defens…
Key Headlines Summary - US waives proposed 100% tariffs on India over Russian oil purchases. - Trump waives/loosens sanctions tied to Russian fossil fuel sales; Russia-related restrictions eased. - Strait of Hormuz tanker fire after hitting a naval mine. - Saudi Arabia raises alerts; air traffic briefly suspended in Dammam amid possible missile threat. - UK FCDO advises against all but essential travel to Saudi Arabi…
Posted without readable text
Key Headlines Summary - Israel-Lebanon air-defense activity continues; interceptor launches over southern Lebanon and “false target” reports. - Yemen/Saudi front remains active: Houthi missile strikes on Aden airport; repeated alerts in Khamis Mushait. - Tabriz, Iran explosion reports add to broader Middle East geopolitical friction. - Oil prices surged; WTI back above $100 and Brent at elevated levels amid supply-ri…
Key Headlines Summary - UK GDP beat expectations for a 4th month; BoE seen with more room to tighten. - Fed path remains clouded by AI-driven growth debate; USD weakens on dovish repricing. - GBP hits 3-week highs vs USD; EUR/USD sentiment remains USD-led. - Japan stablecoin pilot completed by top 3 banks; JPY still lacks strong follow-through. - Middle East risk elevated: Lebanon-Qatar energy deal advances, Syria/Is…
Key Headlines Summary - Air India cancels flights to Riyadh, Dammam, and Jeddah amid an evolving Saudi situation. - French frigate downs drone near a French-owned ship in the Bab el-Mandeb; Red Sea security risk remains elevated. - Houthi forces claim another drone shootdown over Marib; Gulf security friction persists. - Fed Chair Warsh gives no forward guidance, reiterates price stability focus; USD softens. - US Tr…
Key Headlines Summary - Israel/Houthis: Aden explosions; Houthi attacks and Saudi intercepts keep Red Sea/Gulf risk elevated. - Israel/Iran: Netanyahu signals forceful response; IDF alert raised amid reports of Iranian missile drills, launcher rebuild, and possible pre-emptive strike risk. - U.S. military airlift/refueling activity into the Middle East is rising, reinforcing escalation concerns. - Syria: Gas pipeline…
Key Headlines Summary - Hot US CPI/PPI and firm energy/shelter costs keep Fed tightening risk alive. - Risk assets weaken as AI trade unwinds; equities and Asian FX under pressure. - Middle East friction persists: Syria blast reports, Iran missile test, Lebanon/Hezbollah escalation risk, Ukraine/Russia strikes continue. - Brent holds a sizable geopolitical risk premium despite rising Persian Gulf flows. - Eurozone in…
Key Headlines Summary - Ukraine ends restraint; vows renewed strikes on Russian oil refineries after continued attacks on civilian/energy assets. - Israel-Hezbollah front remains active; intense bombardment reported in southern Lebanon. - Iran risk premium elevated: US reportedly weighing major strike options; no ground invasion planned. - Yemen conflict escalates; Houthis threaten more attacks on Saudi airports and …
Showing the 12 most recent of 20 posts we hold for @GeoMarketJournal. 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.
Named by 3 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.
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.
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 24 October 2026 — this entry's latest reading, not the date you are reading this.
“GeoMarket Journal | Global News & Markets” (@GeoMarketJournal), 21 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/GeoMarketJournal.
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.