On-demand and reserved GPU and CPU infrastructure for AI workloads across a global network of enterprise-grade providers --> https://fluence.ai/
All Links: https://linktr.ee/fluencenetwork
Created
Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 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 the other topics.
Growth
65 measurements spanning 96 days, net -8,975. 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 69,154–80,821 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)
Subscribers
Change
10 Nov 2026, 03:17
70,500
-106
8 Nov 2026, 15:59
70,606
-157
7 Nov 2026, 06:51
70,763
-72
6 Nov 2026, 05:21
70,835
-142
5 Nov 2026, 03:00
70,977
-100
4 Nov 2026, 00:37
71,077
-86
3 Nov 2026, 01:17
71,163
-66
2 Nov 2026, 04:31
71,229
-140
1 Nov 2026, 04:40
71,369
-73
31 Oct 2026, 06:46
71,442
-126
30 Oct 2026, 03:50
71,568
-80
29 Oct 2026, 06:55
71,648
-109
28 Oct 2026, 02:30
71,757
-99
27 Oct 2026, 02:59
71,856
-73
26 Oct 2026, 06:17
71,929
-70
25 Oct 2026, 05:47
71,999
-102
24 Oct 2026, 04:58
72,101
-84
23 Oct 2026, 06:25
72,185
-116
22 Oct 2026, 02:50
72,301
-97
21 Oct 2026, 00:10
72,398
first reading
Engagement
30 posts held, back to 6 February 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 194 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.396%
avg views ÷ 70,500 subscribers
Avg views / post
279
1 post measured
Reaction rate
2.51%
reactions ÷ views · ER floor
Posts in window
1
of 30 held
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 4 November 2026
Posts held
30 (6 February 2026 – 4 November 2026)
Views total
279
Reactions total
7
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
10 Nov 2026, 19:56 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.
What this channel posts
Photos
234
Videos
63
Links
407
Lifetime counters from Telegram’s own channel header, read 10 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
2m 01s
Average length
13s
Measured directly from 9 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
394 reactions across 30 posts, in 11 distinct kinds. The most used accounts for 38.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
150
38.1%
❤
88
22.3%
👍
72
18.3%
👏
58
14.7%
🍌
9
2.28%
😁
5
1.27%
🥰
5
1.27%
🎉
2
0.508%
🤩
2
0.508%
🤯
2
0.508%
😢
1
0.254%
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 30 of the 30 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 394 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 30 most recent posts we hold, published 6 February 2026 to 4 November 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
Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
The ar.io gateway network now runs on Solana, and anyone can run a gateway 🖥
We wrote a guide for setting one up on a Fluence VM, and the first 10 operators to join and pass their first epoch get $100 in CPU credits ⭐️
📌 https://fluence.ai/blog/fluence-cpu-credits-ario-gateway/ — the guide covers the VM, Solana keys and a dedicated RPC, since the public one is rate-limited and can drop observer transactions.
Once …
Big news: we’ve just signed a $2.4M contract with WorldEngine AI to support inference workloads for their physical AI stack 🤝
🤖 WorldEngine builds physical AI infrastructure across real-world robotics data, model training, evaluation, and deployment
We’re excited to support the WorldEngine team and provide part of the backbone that turns new models into systems that run in the real world 🚀
Fluence DAO Q3’26 report is out! 📊
Q3 brought a lot of updates across Fluence:
• VPC with private networking and security groups for multi-VM deployments
• x402 payments, allowing AI agents to pay in crypto and rent compute without manual signup
• GPU Cluster Auctions, which facilitated multiple deals worth a combined $26.9M+
• Shared CPU instances, a browser-based Web Terminal, and our move to fluence.ai 🪄
Read t…
Your AI agent can now spin up compute on Fluence 🤖 Fluence MCP is live! ⚡
Connect Cursor, Claude Code, VS Code, Codex, or any other MCP-compatible client, tell your agent what you need, and it handles the rest.
🔗 console.fluence.ai/settings/mcp
Setup takes one config snippet + a Fluence API key. The MCP server is hosted, so there’s nothing to install or keep updated.
Once it's connected, you don't even need to …
AI agents can now pay for their own compute🤑
Fluence Cloud now supports x402 🤖 Top up with USDC on Base, sign in with a wallet, and spin up CPU or GPU resources through the API. No signup or credit card needed.
See how it works ↓
https://fluence.ai/blog/x402-agentic-payments/
VPC is live on Fluence 🔒☁️
Build multi-VM deployments on isolated VPC networks, with subnets, security groups, managed egress, and cloud-init.
Keep databases and backends private, and expose only the VMs that need a public endpoint 🗝
Learn more 👉 https://fluence.ai/blog/fluence-vpc/
September is off to a strong start: we’ve secured another $5.5M deal 🪄
The customer is building AGI to find the shortest path from biology to medicines. We’re helping make sure compute isn’t the bottleneck 🦾
Bring your workload too! Let GPU providers compete for it at Fluence GPU Auctions ⤵️
auctions.fluence.network
Wrapping up a productive summer with some exciting news!
Another $15.4M+ deal secured through Fluence GPU Auctions 🔥🔥🔥
96 H100 nodes across Asia are going into production on Fluence, powering inference and model training
More high-value GPU deals are moving through the platform, connecting serious demand with available capacity through competitive bidding.
Looking for GPUs — or have capacity to sell?
Join the pla…
fluence.network → fluence.ai
We’re moving to a new domain, but this is more than a url change 🌈
Since the beginning of the year, we’ve been doubling down on GPU infrastructure and building Fluence into a cloud business for AI workload — fluence.ai reflects where we’re headed 🚀
Same Fluence, new home. So if you see fluence.ai in your browser, inbox, or links from us — don’t be confused. It’s us 🙌
💥 $6M in GPU cluster contracts — and we’re just getting started!
Since launching Fluence GPU Auctions, demand and supply are already finding their match ⬆️
Need compute? Have capacity?
Join now 👉 https://auctions.fluence.network
Introducing GPU Cluster Auctions — a new way to source reserved GPU capacity on Fluence ⚡
Instead of going back and forth with providers to understand what’s available and at what price, post your requirements once and let providers bid for your request.
Compare offers side by side across price, SLA, fabric, deployment model, and availability.
With short bidding windows, auctions enable GPU cluster price discovery…
Fluence DAO governance is moving to our native Token App 🧑⚖️
You now can vote, create proposals, and follow DAO updates natively in Token App, instead of Tally (as it's being shutting down)
Try now 👉 flt.fluence.network/governance
🔥11❤9🥰4
Showing the 12 most recent of 30 posts we hold for @fluence_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.
Forward network
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.
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 19 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Serge Hexn @SergeHexn · 471,635 Telegram ranks this channel #87 of 87 here — alongside 86 others — read 19 August 2026
GoMining News @gomining · 96,383 Telegram ranks this channel #87 of 88 here — alongside 87 others — read 19 August 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“Fluence” (@fluence_official), 70,500 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/fluence_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.