Channel
@GemHUB_Protocol_official
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
6,330subscribers
-342 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001791297166 |
|---|---|
| Type | Channel |
| Username | @GemHUB_Protocol_official |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/GemHUB_Protocol_official |
Technology — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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 |
|---|---|---|
| 17 Sept 2026, 20:39 | 6,330 | -49 |
| 13 Sept 2026, 17:59 | 6,379 | -35 |
| 9 Sept 2026, 18:41 | 6,414 | -26 |
| 4 Sept 2026, 15:00 | 6,440 | -31 |
| 1 Sept 2026, 08:05 | 6,471 | -31 |
| 29 Aug 2026, 11:28 | 6,502 | -20 |
| 26 Aug 2026, 08:48 | 6,522 | -16 |
| 23 Aug 2026, 08:58 | 6,538 | -23 |
| 20 Aug 2026, 04:07 | 6,561 | -68 |
| 16 Aug 2026, 18:25 | 6,629 | -12 |
| 13 Aug 2026, 10:06 | 6,641 | -11 |
| 10 Aug 2026, 09:28 | 6,652 | -19 |
| 7 Aug 2026, 08:51 | 6,671 | -1 |
| 7 Aug 2026, 01:02 | 6,672 | first reading |
23 posts held, back to 16 October 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pages 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 23 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
10 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 70.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 70.0% | |
| 🔥 | 2 | 20.0% | |
| 👍 | 1 | 10.0% |
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 6 of the 23 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 16 October 2025 to 11 August 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.
[Notice] New Official GemHUB X (formerly Twitter) & Security Alert Dear GemHUB Community, Following our initial report to the platform team regarding the security incident, we have set up a new official X (formerly Twitter) account to ensure your safety and prevent further damage. 📢 New Official GemHUB X Account: https://x.com/GHUB_GemHUB ⚠️ DO NOT VISIT THE PREVIOUS X ADDRESS The previous handle may now be contr…
[Notice] Update on Official GemHUB X (Twitter) Account Restoration Dear GemHUB Community, We would like to share an update regarding the restoration of our official X ( Twitter) account. Our team has successfully regained access to the account and immediately implemented enhanced security measures. However, due to the incident, many of our previous posts and channel details were deleted. As a result, the account …
[Notice] Official GemHUB X (Twitter) Account Compromised Dear GemHUB Community, Please be advised that the official GemHUB X (Twitter) account has been compromised and subsequently deleted, making it currently inaccessible. Upon detecting the issue, our team immediately reported the incident to X support and requested urgent intervention. We are doing everything possible to restore the account as quickly as possib…
📢 BitMart Exchange Service Termination The GemHUB Team would like to inform you that BitMart, one of the exchanges where GHUB is currently listed, has officially announced its plan to cease platform operations. If you are using BitMart, please review the following schedule and make the necessary arrangements to avoid any inconvenience. ■ BitMart Service Termination Schedule *July 26, 2026, 01:30 UTC > Suspension o…
❤1
📢 Coinone Event: Get a Bonus When You Trade GHUB! A GHUB trading event is currently underway on Coinone. You’ll receive a bonus when you trade 5,000 Won or more during the event period. 📆 Event Period June 25, 2026 (Thu) 10:00 AM – June 28, 2026 (Sun) 11:59 PM (Note: The event may end early due to budget exhaustion or other reasons.) Please refer to the announcement below for more details 👇 🔗 https://coinone.co.k…
GOPAX GHUB Daily Trading King Event Announcement Gopax is hosting a GHUB partnership event: the Daily Trading King Event. We look forward to your interest and participation, and hope you enjoy the generous rewards. <Event Schedule> 📆 Event Period: June 15, 2026 (Mon) 00:00:00 – June 24, 2026 (Wed) 23:59:59 (KST) (10 days) 📆 Reward Distribution Date: Wednesday, July 15, 2026 For more details, please refer to the Go…
📢 GemHUB Expands Web3 Ecosystem with EOS RED, Fortress 3 Blue, and Cooking Adventure! We are thrilled to announce a major expansion of our global Web3 gaming ecosystem. Three legendary gaming IPs are officially onboarding onto GemHUB: 🎯EOS RED – The classic hardcore MMORPG with a massive, loyal global player base. 🎯Fortress 3 Blue – The legendary casual shooting IP, preparing for PC/Mobile cross-platform launch. 🎯C…
GHUB Token Unlock Schedule Update for Web3 Gaming Ecosystem Expansion The GemHUB project would like to announce an adjustment to our token circulation plan in order to maintain a healthier trading environment, expand the global Web3 gaming ecosystem, and strengthen the foundation for multi-chain operations. In accordance with our 2026 roadmap, GemHUB is preparing to integrate with various Web3 gaming projects such …
BPMG, the developer and operator of GemHUB, is joining forces with Welcome Payments (an IT financial payment specialist under Welcome Financial Group) and VDCRUX (an online/offline payment and ordering service provider) to co-develop a stablecoin-based payment business. You can find the full news coverage in the link below: 👉 Read the full article here The partnership aims to build a practical payment environment u…
❤2🔥1
🚀GemHUB New Website & Whitepaper Launch!🚀 A new era for GemHUB has begun! Our official website and whitepaper have been updated. 🚀 This update focuses on structural innovation and enhancing User Experience (UX) to position GemHUB as a leader in the global mainstreaming of Web3. ▣ Key Highlights 🌐 Website Renewal: Redesigned with a simpler, more intuitive interface. 📄 Whitepaper : Updated core strategies and tokeno…
GemHUB Multichain Expansion and 2026 Token Unlock Schedule Updated As we prepare for global expansion and the construction of a robust multichain ecosystem, we would like to share an update regarding our 2026 Token Circulation Plan. This adjustment is designed to maintain a healthy trading environment while fueling our next phase of growth. According to our 2026 roadmap, GemHUB is initiating its multichain expans…
📢 고팍스 GHUB 거래왕 & N빵 이벤트 안내 안녕하세요, 젬허브 팀입니다. 고팍스 거래소에서 GHUB 데일리 거래왕 & 100% 에어드랍 이벤트를 진행합니다. 많은 관심과 참여를 부탁드리며, 풍성한 혜택 받아 가시기를 바랍니다. 📆 이벤트 기간 - 이벤트 기간: 2026년 03월 19일(목) 00:00 ~ 2026년 03월 28일(토) 23:59 (KST) (10일 간) - 리워드 지급일: 2026년 04월 15일(수) 자세한 내용은 아래 고팍스 공지를 참고해 주세요 👇 🔗 https://www.gopax.co.kr/notice/detail?id=2365 젬허브는 안정적인 거래 환경 조성과 건강한 시장 형성을 위해 지속적으로 노력하겠습니다. 커뮤니티 여러분의 많은 관심과 참여 부탁드립니다 🙌 감사합니다. — 젬허브 팀 🚀
Showing the 12 most recent of 23 posts we hold for @GemHUB_Protocol_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.
Named by 5 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“GemHUB_Protocol_official” (@GemHUB_Protocol_official), 6,330 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/GemHUB_Protocol_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.