Channel
@globiance
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,317subscribers
-73 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001490541501 |
|---|---|
| Type | Channel |
| Username | @globiance |
| Created | Between 1 May 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/globiance |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 06:20 | 1,317 | -6 |
| 30 Sept 2026, 04:18 | 1,323 | -11 |
| 15 Sept 2026, 18:15 | 1,334 | -3 |
| 11 Sept 2026, 18:01 | 1,337 | -2 |
| 7 Sept 2026, 10:37 | 1,339 | -7 |
| 2 Sept 2026, 20:26 | 1,346 | -6 |
| 31 Aug 2026, 02:19 | 1,352 | -5 |
| 27 Aug 2026, 15:56 | 1,357 | -6 |
| 24 Aug 2026, 10:17 | 1,363 | -1 |
| 20 Aug 2026, 11:52 | 1,364 | -4 |
| 17 Aug 2026, 20:54 | 1,368 | -5 |
| 14 Aug 2026, 15:28 | 1,373 | -12 |
| 10 Aug 2026, 20:21 | 1,385 | -5 |
| 7 Aug 2026, 08:15 | 1,390 | no change |
| 7 Aug 2026, 08:07 | 1,390 | first reading |
20 posts held, back to 11 June 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
📢 Your Refunded XDC. Your Choice. More Possibilities. As the XDC refund process goes on, eligible users who have received their refund can now freely access their unlocked XDC. Whether you choose to withdraw your XDC or explore new opportunities, the ball is in your court. We're also excited to introduce Globiance Trade, our newly launched trading platform, designed to provide a faster, smoother, and more powerful tr…
📢 XDC Withdrawal Update If you have received the refund email your XDC balance has been unlocked in your Globiance account and your XDC is now available for withdrawal. Simply log in to your Globiance account to access and withdraw your available XDC. If you require any assistance with logging in, KYC verification, or the withdrawal process, our support team is here to help. 📧 Email: [email protected]…
🎉 Globiance XDC Refund Milestone Update We are pleased to announce another important milestone in the Globiance refund process. ✅ All users included in the last refund email (up to 138,000 XDC) can now withdraw their refunded XDC. This milestone reflects our continued commitment to processing refunds securely, accurately, and transparently for all eligible users. We sincerely appreciate the patience, trust, and c…
📢 Globiance Refund Progress Update 2026-07-08 ✅ 78.14% total refunds completed ✅ 100% HK refunded ✅ 100% SG refunded ✅ 100% BR refunded ✅ 99.50% AU refunded ✅ 65.39% JP refunded Steady progress continues as refund batches are processed globally. https://globiance.com/news/globiance-refund-progress-update-regional-milestones-2026-07-08.html
📢 Globiance Refund Progress Update 2026-07-07 ✅ 78.02% total refunds completed ✅ 100% HK refunded ✅ 100% SG refunded ✅ 100% BR refunded ✅ 99.50% AU refunded ✅ 65.25% JP refunded Steady progress continues as refund batches are processed globally. https://globiance.com/news/globiance-refund-progress-update-regional-milestones-2026-07-07.html
📢 Globiance Refund Progress Update 2026-07-06 ✅ 77.90% total refunds completed ✅ 100% HK refunded ✅ 100% SG refunded ✅ 100% BR refunded ✅ 99.50% AU refunded ✅ 64.96% JP refunded Steady progress continues as refund batches are processed globally. https://globiance.com/news/globiance-refund-progress-update-regional-milestones-2026-07-06.html
📢 Globiance Refund Progress Update 2026-07-03 ✅ 77.78% total refunds completed ✅ 100% HK refunded ✅ 100% SG refunded ✅ 100% BR refunded ✅ 99.50% AU refunded ✅ 64.82% JP refunded Steady progress continues as refund batches are processed globally. https://globiance.com/news/globiance-refund-progress-update-regional-milestones-2026-07-03.html
📢 Globiance Refund Progress Update 2026-06-30 ✅ 77.43% total refunds completed ✅ 100% HK refunded ✅ 100% SG refunded ✅ 100% BR refunded ✅ 99.50% AU refunded ✅ 64.26% JP refunded Steady progress continues as refund batches are processed globally. https://globiance.com/news/globiance-refund-progress-update-regional-milestones-2026-06-30.html
📢 Globiance Refund Progress Update 2026-06-29 ✅ 77.32% total refunds completed ✅ 100% HK refunded ✅ 100% SG refunded ✅ 100% BR refunded ✅ 99.50% AU refunded ✅ 64.11% JP refunded Steady progress continues as refund batches are processed globally. https://globiance.com/news/globiance-refund-progress-update-regional-milestones-2026-06-29.html
📢 Globiance Refund Progress Update 2026-06-26 ✅ 77.20% total refunds completed ✅ 100% HK refunded ✅ 100% SG refunded ✅ 100% BR refunded ✅ 99.50% AU refunded ✅ 63.83% JP refunded Steady progress continues as refund batches are processed globally. https://globiance.com/news/globiance-refund-progress-update-regional-milestones-2026-06-26.html
📢 Globiance Refund Progress Update 2026-06-25 ✅ 77.08% total refunds completed ✅ 100% HK refunded ✅ 100% SG refunded ✅ 100% BR refunded ✅ 99.25% AU refunded ✅ 63.55% JP refunded Steady progress continues as refund batches are processed globally. https://globiance.com/news/globiance-refund-progress-update-regional-milestones-2026-06-25.html
📢 Globiance Refund Progress Update 2026-06-23 ✅ 76.85% total refunds completed ✅ 100% HK refunded ✅ 100% SG refunded ✅ 100% BR refunded ✅ 99.25% AU refunded ✅ 63.12% JP refunded Steady progress continues as refund batches are processed globally. https://globiance.com/news/globiance-refund-progress-update-regional-milestones-2026-06-23.html
Showing the 12 most recent of 20 posts we hold for @globiance. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“Globiance Exchange Official” (@globiance), 1,317 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/globiance.
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.