Telegram RegisterThe public register of Telegram
Telegram profile photo for Fog Hashing & Liquid Mining

Channel

Fog Hashing & Liquid Mining

@foghashingchannel

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

334subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001918893927
TypeChannel
Username@foghashingchannel
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/foghashingchannel

Growth

333334333.57 August 2026 — 333 subscribers8 August 2026 — 333 subscribers15 August 2026 — 334 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net +1. 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 333–334 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 00:16334+1
8 Aug 2026, 07:05333no change
7 Aug 2026, 11:40333first reading

Engagement

16 posts held, back to 31 December 2025the 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.

ERR · 30 days
35.3%
avg views ÷ 334 subscribers
Avg views / post
118
1 post measured
Reaction rate
4.24%
reactions ÷ views · ER floor
Posts in window
1
of 16 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
WindowRolling 30 days · latest post in window 21 July 2026
Posts held16 (31 December 202521 July 2026)
Views total118
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 07:05 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

Video runtime
2m 36s
Average length
52s

Measured directly from 3 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

61 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 31.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1931.1%
🔥1829.5%
1626.2%
58.20%
👏23.28%
🥰11.64%

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

Measured over the 16 most recent posts we hold, published 31 December 2025 to 21 July 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

21 Jul 2026, 14:04 UTC118 views5 reactionsread 8 August 2026
Photo

Guess how many NVIDIA RTX PRO 6000 GPUs will be immersed in this container?

🔥3👍1🥰1

9 Jul 2026, 13:32 UTC198 viewsread 8 August 2026
Photo

Not every AI deployment needs the biggest GPU. Inference demand keeps climbing. Meanwhile, a lot of real power at the edge sits underused, waiting for its AI moment. We've been talking with a few mining operators who want to move into AI. For most sites, the real opportunity isn't an AI factory. It's a right-sized turnkey AI pilot, quick to deploy while the market's still early. One pairing we like is the RTX PRO

7 Jul 2026, 15:20 UTC199 viewsread 8 August 2026
Video

A 110 petahash Bitcoin site in Missouri, and it's quiet enough to hold a conversation right out front. That's Wade's self-mine farm, running two of our immersion containers for about a year now. He spent years on air-cooled miners first. Dirt, noise, heat. Then he converted his S21s to #immersion, runs them on @Braiins software, and now says he's never going back. The classic BC40 Pro and the second-gen BC40 Elite,

6 Jul 2026, 14:46 UTC157 viewsread 8 August 2026
Video

10MW HC40-S2400 hydro containers on the ground at Simple Mining's campus in Iowa, hashing for 60 days now. Simple Mining is one of the sharpest hosting operators in North America. They sell, host, and repair in-house, and their on-site ops team knows exactly what they're running. Glad to have them running on Fog Hashing.

22 Jun 2026, 07:30 UTC185 views1 reactionsread 8 August 2026

6MW immersion cooling, now live in North Dakota. Deploying a 6MW mining site here takes more than good hardware. It demands navigating some of the toughest regulatory and climate bars in North America. We energized this high-density site by meeting the state's strict electrical code: PDC CSA certified, as North Dakota requires. Rest of the electrical componants: UL certified. Compliance is only half of it. North Da

1

4 Jun 2026, 02:42 UTC254 views5 reactionsread 8 August 2026

Fog Hashing is launching a new product line: Fog Power. For years, we've cooled high-density compute across 40+ countries. The same thing kept stalling sites, not the chips, the power gear. So we took on the power side ourselves, grid to rack, delivered in weeks. Read why 👇 https://foghashing.io/blog/power-gear-in-weeks-introducing-fog-power

🔥5

13 Apr 2026, 14:32 UTC360 views8 reactionsread 8 August 2026
Photo

Night falls, hashrate live. Behind every setup, it's in-house engineering, mature manufacturing and iteration from real operations.

👍43🔥1

10 Apr 2026, 10:26 UTC331 views4 reactionsread 8 August 2026
Photo

🥂 Join us at the #Bitcoin2026 Las Vegas Cocktail Hour ! 🗓️ Monday, April 27 | 9:00 PM – 00:00 AM 📍 Conrad Las Vegas at Resorts World, 66th Floor A premium networking party hosted by MicroBT, Fog Hashing and RepairBit. Open bar, great view from the 66th floor, good mix of mining, energy and AI/HPC. 👉 Register at https://luma.com/bd5vpuwt , See you there.

👏21👍1

13 Mar 2026, 03:33 UTC339 views4 reactionsread 8 August 2026
Photo

Everyone's talking about AI data centers. Few are talking about how to fund them from day one. At the MicroBT M70 Global Launch, our VP Nick Burley laid out the playbook: Secure power first. Mine for day-one revenue. Transition to AI when you're ready. The physics backs this up. Whether the chip is hashing SHA-256 or running inference, the infrastructure challenge is identical: high density, massive heat, liquid c

👍31

30 Jan 2026, 15:44 UTC370 views10 reactionsread 8 August 2026
Photo

It’s always a beautiful scene — liquid cooling containers going live in vast, quiet landscapes.

🔥9👍1

28 Jan 2026, 15:22 UTC338 views7 reactionsread 8 August 2026

⚠️ We have recently become aware of impersonation attempts targeting our team's accounts. Please take note of the following security guidelines: ✅ Zero-Trust Policy: Our company and management will NEVER ask you for urgent transfers, sensitive information, or to click on suspicious links. DO NOT install suspicious software or run unknown command lines. ✅ Official Channels Only: All official announcements are issued

👍7

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

Mentions

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.

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

“Fog Hashing & Liquid Mining” (@foghashingchannel), 334 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/foghashingchannel.

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.