Channel
@w3binfinity
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,155subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001616900142 |
|---|---|
| Type | Channel |
| Username | @w3binfinity |
| Created | Between 1 December 2021 and 6 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 2 times, most recently 11 August 2026 |
| On Telegram | t.me/w3binfinity |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 06:35 | 1,155 | no change |
| 8 Aug 2026, 00:15 | 1,155 | first reading |
20 posts held, back to 6 March 2023 — 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 pageof 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 8 May 2023. An engagement rate over an empty window would be a number about nothing.
15 reactions across 8 posts, in 2 distinct kinds. The most used accounts for 73.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 11 | 73.3% | |
| ❤ | 4 | 26.7% |
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 8 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 15reactions 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 6 March 2023 to 8 May 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
👋 Quick update! Good news! You can now claim your tokens on our platform at https://private.w3binfinity.io. If you encounter any issues, please reach out to Odin on Telegram at @odinsd and he'll be happy to help you out. Stay tuned for more exciting updates and new features in the coming weeks!
Quick update! Hi folks, We are currently fixing the claim function to pay tokens and will be integrating new features soon. Hope you understand and cooperate with us! https://twitter.com/w3binfinity/status/1654075821588619265
With relentless dedication, the development of W3BWallet is almost complete and it is now approaching the testnet phase. If you're interested in being among the first to try out this product, please do not hesitate to inform us. Thanks for your support. Stay tuned! https://twitter.com/w3binfinity/status/1652013357631934464
❤1
Get ready, #Bitcoin enthusiasts! The upcoming halving event is a major milestone that highlights the digital currency's ability to self-regulate and maintain its scarcity. As we continue to see increasing adoption and mainstream interest, the future of #BTC looks bright! https://twitter.com/w3binfinity/status/1648364183665389569
Calling all blockchain enthusiasts! We need a skilled Community Manager to join our team and help grow our vibrant community. Shape the future of blockchain and drive engagement with our project by applying now. DM us on Telegram @odinsd to apply!
Follow W3B Analytics to get ready to unlock some amazing rewards! The Token Unlock Schedule is happening soon. Keep an eye out for more details and be sure to set a reminder! #Web3 #Token #W3b #Analytics https://twitter.com/w3binfinity/status/1644369187614384130
Consider this impressive statistic as evidence of the potential of blockchain and DeFi projects. Together, let's empower DeFi to shape the future, and let W3B lead the way to success! https://twitter.com/w3binfinity/status/1643646850334072834
Hi everyone, This is just a friendly reminder that the WBY event staking to receive HOOK will be ending today. However, we're excited to announce that we'll be running a new and even more fantastic event soon. Stay tuned for the upcoming update and thank you for your support! https://twitter.com/w3binfinity/status/1641112147794210817?s=46&t=tp5BAwNuBAKEp7WWN9cOXQ
Attention community: Our system has a minor issue with claiming V2 tokens, resulting in only 9.7% being claimable instead of the intended 10%. Our dev team is working on a fix, and you'll be compensated next month. Apologies for any inconvenience. Thank you for your support! https://twitter.com/w3binfinity/status/1641073480505626625?s=46&t=tp5BAwNuBAKEp7WWN9cOXQ
Quick update: We've just done the next conversion of V1 tokens to V2 and distributed them to users. Kindly check it out and please feel free to contact us if you have any questions. Thanks and stay tuned for the next launch! https://twitter.com/w3binfinity/status/1640528880506159108
New product announcement We're thrilled to announce the launch of W3BAnalytics - an innovation that will revolutionize the way you do things on the blockchain! And besides that, we're hiring a research team to help us run the program. Contact us for more info! #Web3 #Analytics https://twitter.com/w3binfinity/status/1637464153144299523
#AMA IS NOW LIVE https://binance.me/en/live/video?roomId=2125941 https://twitter.com/w3binfinity/status/1635628535984320514
Showing the 12 most recent of 20 posts we hold for @w3binfinity. 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.
Citation-graph rank — 966,948 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
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.
@w3binfinity named 5 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“W3binfinity Official” (@w3binfinity), 1,155 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/w3binfinity.
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.