Telegram RegisterThe public register of Telegram
Telegram profile photo for Web3Hub | Official

Channel

Web3Hub | Official

@Web3HubPro

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

832subscribers

+2 since we began measuring on 8 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002421598239
TypeChannel
Username@Web3HubPro
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 September 2026
Last confirmed live29 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/Web3HubPro

Topic

Marketing & affiliate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 2026 and assigned it the closest of 31 fixed categories, at 70% 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 the other topics.

Growth

829832830.58 September 2026 — 830 subscribers8 September 2026 — 830 subscribers19 September 2026 — 829 subscribers13 October 2026 — 831 subscribers21 October 2026 — 830 subscribers29 October 2026 — 832 subscribers8 September 202629 October 2026
6 measurements spanning 52 days, net +2. 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 829–832 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Oct 2026, 21:27832+2
21 Oct 2026, 21:46830-1
13 Oct 2026, 23:00831+2
19 Sept 2026, 00:17829-1
8 Sept 2026, 05:22830no change
8 Sept 2026, 04:47830first reading

Engagement

20 posts held, back to 13 August 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 September 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

161 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 41.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6741.6%
👏2314.3%
🤩1811.2%
🏆169.94%
🔥116.83%
😍116.83%
⚡84.97%
🤝63.73%
😎10.621%

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 20 of the 20 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 161 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 13 August 2026 to 5 September 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.

Recent posts

5 Sept 2026, 16:28 UTC116 views8 reactionsread 8 September 2026

Official Announcement — V2 to V3 Transition The Final 90 Days of V2 — The Beginning of Web3Hub V3 Priority: High Announcement Date: September 5, 2026 Transition Period: October–December 2026 V3 Launch: January 2027 Dear Web3Hub Community, Since its inception, Web3Hub has continuously developed its economic architecture with a focus on balancing Community Growth, User Participation, and Ecosystem Development. As we ap…

❤3⚡1🏆1👏1🤩1😍1

5 Sept 2026, 16:28 UTC153 views9 reactionsread 8 September 2026

7. V2 vs. V3 Service Fee V2: 10% V3: 10% CCC V2: 30% V3: 30% Promotion / Incentive V2: 2X CCC — November & December 2026 V3: EGIP — 30% APB & CIB V2: Three-Level Structure V3: APB → Presenter ID — 10% Agent V2: 5% V3: Removed Sales Associate V2: 2.5% V3: Removed Consultant V2: 2.5% V3: Removed Ecosystem Partner V2: — V3: 10% Discount V2: Up to 30% in October 2026 V3: Removed Economic Model V2: Community & Referral V3…

❤4⚡1🏆1👏1🤩1😍1

5 Sept 2026, 16:28 UTC75 views10 reactionsread 8 September 2026
Photo

Photo, posted without a caption

👏3🔥2⚡1❤1🤩1😍1😎1

5 Sept 2026, 16:24 UTC101 views7 reactionsread 8 September 2026

Official Announcement Web3Hub: One Step Closer to a Decentralized Service Economy Priority: High 🔴 Date: September 5, 2026 — 14:00 UTC Implementation: January 2027 Dear Web3Hub Community, From the beginning, Web3Hub has been designed to connect digital ownership, access to services, and community-driven economic participation within a Web3 infrastructure. Under the current model, users who claim an NFT enter a largel…

❤3🏆1👏1🤩1😍1

5 Sept 2026, 16:23 UTC91 views6 reactionsread 8 September 2026
Photo

Photo, posted without a caption

❤2🏆1🔥1🤩1😍1

5 Sept 2026, 13:05 UTC148 views12 reactionsread 8 September 2026

📣 Official Announcement — Web3Hub’s Vision for the Next Generation of NFTs Sub-Category: Web3 Infrastructure & The Future of NFTs Priority: Medium 🟠 Date: September 5 , 2026 12:00 utc Anticipating the Future of NFTs: When Web3Hub Moved Several Steps Ahead Dear Web3Hub Community, The initial concept and architecture of Web3Hub were developed in Q4 2024 based on a clear assessment of the future trajectory of the NFT ma…

❤7🏆1👏1🤝1🤩1😍1

5 Sept 2026, 13:04 UTC143 views7 reactionsread 8 September 2026
Photo

Photo, posted without a caption

❤2👏2🏆1🤩1😍1

24 Aug 2026, 14:58 UTC308 views9 reactionsread 8 September 2026

🚨 Web3Hub MetaBusiness Rejection Reason & Resubmission Update A new Rejection Reason section has been added to the MetaBusiness profile status. ━━━━━━━━━━━━━━━━━━ 🔴 Rejection Reason If an advertisement is Rejected by the administration team, the specific reason for rejection will now be displayed directly in the Profile Status section. Users can review the provided feedback and clearly understand which part of their …

❤5👏2🤝1😍1

24 Aug 2026, 14:48 UTC212 views8 reactionsread 8 September 2026

🚀 Web3Hub MetaBusiness Preview & Admin Approval Update We are pleased to announce a new Preview section in the MetaBusiness module, designed to provide users with a more transparent and reliable review process before submitting an advertisement for Admin Approval. ━━━━━━━━━━━━━━━━━━ 👁 1. Preview Before Submission The new Preview feature allows users to view their advertisement exactly as it will appear to other users…

❤4🏆1👏1🤝1😍1

Showing the 12 most recent of 20 posts we hold for @Web3HubPro. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 1 registered channel — 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.

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

“Web3Hub | Official” (@Web3HubPro), 832 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/Web3HubPro.

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.