Telegram RegisterThe public register of Telegram
Telegram profile photo for SnowCore.io

Channel

SnowCore.io

@snowhosting

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

199subscribers

-2 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-1002644402517
TypeChannel
Username@snowhosting
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/snowhosting

Growth

199202200.57 August 2026 — 201 subscribers8 August 2026 — 201 subscribers8 August 2026 — 202 subscribers22 August 2026 — 199 subscribers7 August 202622 August 2026
4 measurements spanning 15 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 199–202 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 22:06199-3
8 Aug 2026, 21:01202+1
8 Aug 2026, 11:31201no change
7 Aug 2026, 23:36201first reading

Engagement

20 posts held, back to 6 March 2026the 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
73.3%
avg views ÷ 199 subscribers
Avg views / post
146
5 posts measured
Reaction rate
7.27%
reactions ÷ views · ER floor
Posts in window
5
of 20 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 31 July 2026
Posts held20 (6 March 202631 July 2026)
Views total729
Reactions total53
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 11:31 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.

Reaction mix

118 reactions across 18 posts, in 14 distinct kinds. The most used accounts for 23.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👏2823.7%
2521.2%
🔥2218.6%
🤯1613.6%
👀54.24%
🥰54.24%
👍43.39%
🗿43.39%
😁43.39%
🌚10.847%
💘10.847%
💯10.847%
🙏10.847%
🤪10.847%

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 18 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 118reactions 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 2026 to 31 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

31 Jul 2026, 04:05 UTC120 views6 reactionsread 8 August 2026

As a small thank you for your patience and understanding during the recent network issues, which have now been completely resolved, we've created a 30% discount code for VPS Servers: NewSnow30 The code is limited to the first 50 uses, so make sure to claim it while it's still available. Thank you once again for your trust and support ❤️❄️

3🥰3

29 Jul 2026, 20:02 UTC152 views6 reactionsread 8 August 2026

Another update: More routes have been added, and the global ping has improved. By around 2 a.m. UTC, everything will be running as usual on the network. Next, all VPS nodes will be restarted one after another to apply the network changes: For VPS customers, if DHCP isn’t working for you for any reason, I’ve set up a new web-based VNC browser that you can use to reset your password and modify the network configurati

👏32🤯1

29 Jul 2026, 19:06 UTC147 views12 reactionsread 8 August 2026

We are happy to announce that the issue has been resolved! We are now beginning to respond to all messages and tickets. We have credited each VPS with 5 days of service time. Please note that some routes may still be pending and will be automatically assigned in the next few hours. If you need assistance, please feel free to resend your messages this time :) Thanks for your trust in our services ❤️❄️

🔥63🗿2👏1

29 Jul 2026, 08:19 UTC152 views20 reactionsread 8 August 2026

87.x is now also affected, we are already working on a solution for this as well - apologies for the inconvenience

🤯15👀2🔥2🌚1

28 Jul 2026, 18:32 UTC158 views9 reactionsread 8 August 2026

We're having issues with our IP provider; all IP addresses starting with 194.x are affected

👀3🗿2🥰2💘1💯1

18 Jul 2026, 22:09 UTC220 views1 reactionsread 8 August 2026

Dedicated Servers in stock again! https://snowcore.io/dedicated-server

🤪1

6 Jul 2026, 22:38 UTC291 viewsread 8 August 2026

For everyone asking: https://github.com/V4bel/Januscape https://thehackernews.com/2026/07/16-year-old-linux-kvm-flaw-lets-guest.html This is due to Januscape (CVE-2026-53359), a 16-year-old use-after-free vulnerability in Linux KVM that can allow a guest VM to escape to the host under certain conditions. While the public PoC currently demonstrates a host crash (DoS), a full guest-to-host escape has been reported to

6 Jul 2026, 22:20 UTC221 views7 reactionsread 8 August 2026

We will perform an emergency reboot of all nodes over the next few hours due to a kernel security vulnerability. Each node will be rebooted, and all virtual machines (VMs) will be started again immediately afterward.

👏7

21 Jun 2026, 11:10 UTC276 views3 reactionsread 8 August 2026

New Dedicated Servers available! https://snowcore.io/dedicated-server

🔥21

14 Jun 2026, 12:44 UTC316 views5 reactionsread 8 August 2026

New Dedicated Server Updates! ❄️ Dedicated Servers are now available with fully automated deployment 24/7 - no delays, no waiting for support, and instant provisioning after payment We're also preparing a new restock, more Dedicated Servers will be available soon. Stay tuned! Already own a Dedicated Server with us? Please open a support ticket or send us a message on Telegram so we can add it to the new automated

🔥5

2 Jun 2026, 18:49 UTC312 views5 reactionsread 8 August 2026

The payment issues have been resolved! Payments should now be working properly again :)

👏5

27 May 2026, 16:02 UTC346 views6 reactionsread 8 August 2026

VPS Node #7 restored, RAID failure, no data loss and fully recovered

👏6

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

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

“SnowCore.io” (@snowhosting), 199 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/snowhosting.

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.