Telegram RegisterThe public register of Telegram
Telegram profile photo for VDSok.guru

Channel

VDSok.guru

@vdsokguru

2 usernames

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

570subscribers

-127 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-1002531996985
TypeChannel
Usernames@richshost @vdsokguru
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 live30 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/vdsokguru

Growth

570697633.57 August 2026 — 697 subscribers8 August 2026 — 695 subscribers8 August 2026 — 697 subscribers8 August 2026 — 691 subscribers15 August 2026 — 635 subscribers16 August 2026 — 578 subscribers23 August 2026 — 579 subscribers23 August 2026 — 581 subscribers30 August 2026 — 570 subscribers7 August 202630 August 2026
9 measurements spanning 22 days, net -127. 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 551–716 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 11:07570-11
23 Aug 2026, 21:58581+2
23 Aug 2026, 11:19579+1
16 Aug 2026, 15:35578-57
15 Aug 2026, 07:06635-56
8 Aug 2026, 05:11691-6
8 Aug 2026, 02:19697+2
8 Aug 2026, 00:05695-2
7 Aug 2026, 23:15697first reading

Engagement

20 posts held, back to 21 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 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
25.4%
avg views ÷ 570 subscribers
Avg views / post
145
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
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 3 August 2026
Posts held20 (21 March 20263 August 2026)
Views total145
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:19 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

54 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 46.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54449371960018280472546.3%
custom 52673740696400791171629.6%
custom 526726026159666984259.26%
custom 544530849592456787559.26%
custom 544512420317286388935.56%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 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 54reactions 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 21 March 2026 to 3 August 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.

Telegram Stars

Stars received
8
across the posts below
Posts paid on
5
of 20 we hold a reading for · 25%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @vdsokguru. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 21 March 2026 to 3 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

3 Aug 2026, 16:55 UTC145 viewsread 8 August 2026

Уважаемые клиенты! На данный момент наблюдаются проблемы с DE локацией, в 23:00 по Москве пройдут тех. работы и панель будет опять работать. Сервера работают UPD: Готово 🔗 Наша тема на LolzTeam - https://lolz.live/threads/8981756/ 🔗 Заказать сервер — my.vdsok.guru Поддержка в Telegram - @vdsok_support С уважением, команда VDSok.guru

26 Jul 2026, 15:00 UTC372 viewsread 8 August 2026

🎉 Розыгрыш завершен! 🏆 Победители: 1. @voidlyOwner 2. @Chetyrko 3. @iqoonemoshi88 4. @ctles 5. @TimTarAn 🔍 Проверить результаты

22 Jul 2026, 14:51 UTC547 views2 reactions2 Starsread 8 August 2026

(Чтобы принять участие нажмите кнопку под постом)

custom 52672602615966698421custom 54449371960018280471

22 Jul 2026, 14:50 UTC≈1,850 views13 reactions2 Starsread 8 August 2026

🔥Нам 1 ГОД! VDSok празднует свой первый день рождения! 🎉 Ровно год назад мы запустили проект. Этот год был по-настоящему диким, сложным и безумно крутым. За это время мы вместе с вами прошли через многое: ⚡️Разворачивали сеть, переезжали по ночам в ММТС-9 и переносили виртуалки на SolusVM 2. ⚡️Ставили топовое железо от Arista и боролись с отключениями света в дата-центре. ⚡️Расширяли линейку тарифов — от базовых Xe

custom 52673740696400791178custom 54449371960018280474custom 52672602615966698421

8 Jul 2026, 20:57 UTC494 views3 reactionsread 8 August 2026

🇩🇪 Продолжаем вас радовать — линейка HI-CPU теперь в Германии. ⚡️ Процессоры Intel Core i9-12900K ⚡️ Быстрая DDR4 RAM ⚡️ Надёжные NVMe диски 🛡 Гигабит с защитой Anti-DDoS. 🤝 Напоминаем, что мы платим целых 40% за каждого приведённого клиента по нашей реферальной программе. 🔗 Заказывай сервер — https://my.vdsok.guru/index.php?rp=/store/intel-core-hi-cpu-de 💵 Скидка 40% по промокоду — DXBT58L46V (Количество активаци

custom 54449371960018280472custom 52673740696400791171

8 Jul 2026, 11:40 UTC424 views7 reactions1 Starread 8 August 2026

Важная информация! 🛡 Сегодня в 0:00 по МСК начнутся срочные технические работы на всех наших узлах. Что делаем? Устанавливаем критическое обновление безопасности ядра на хост-машины и перезагружаем их. Почему это нужно? На днях была обнаружена серьезная уязвимость гипервизоров. Защита ваших данных и изоляция виртуальных машин — наш абсолютный приоритет, поэтому мы обязаны оперативно закрыть эту брешь. Что будет?

custom 54449371960018280475custom 52673740696400791172

5 Jul 2026, 22:38 UTC351 views14 reactions2 Starsread 8 August 2026

🇩🇪 Новая локация — Германия, Франкфурт! Мы запустили новые PROMO VPS на немецкой площадке. Которые уже доступны к заказу. ⚡️ Процессоры Intel Core i9-9900K ⚡️ Быстрая DDR4 RAM ⚡️ Надёжные NVMe диски 🛡 Новая L3/L4 Anti-DDoS защита 🤝 Напоминаем, что мы платим целых 40% за каждого приведённого клиента по нашей реферальной программе. 🔗 Заказывай сервер — https://my.vdsok.guru/index.php?rp=/store/intel-core-promo-de 💵

custom 52673740696400791174custom 54449371960018280474custom 54451242031728638893custom 54453084959245678753

23 May 2026, 01:59 UTC739 viewsread 8 August 2026

Уважаемые клиенты! Начинаются технические работы в RU локации для улучшения стабильности всего. Что делаем? Улучшаем сетевую инфраструктуру и систему электропитания на узлах RU локации. Почему это нужно? Чтобы в будущем избежать ситуаций с отключением питания и обеспечить более стабильную работу ваших серверов. Работы повысят отказоустойчивость всей инфраструктуры. Что будет? Во время работ возможно кратковременн

12 May 2026, 19:33 UTC641 viewsread 8 August 2026

Уважаемые клиенты! Ryzen нода восстановлена. Из-за отключения питания произошло повреждение файловой системы на диске. Данные не пострадали, файловая система восстановлена, нода работает в штатном режиме. Почему так заняло долго? Инженер был далеко от серверов и мы не могли срочно исправить проблему. Попытаемся исправить наши ошибки. Благодарим за понимание! Компенсации будут выданы. Если у вас есть вопросы - п

12 May 2026, 13:01 UTC507 views2 reactionsread 8 August 2026

Уважаемые клиенты! Мы знаем о проблеме и уже занимаемся решением. Если у вас есть вопросы - пишите в тикеты my.vdsok.guru или @vdsok_support. С уважением, команда VDSok.guru

custom 54449371960018280472

2 May 2026, 12:13 UTC627 viewsread 8 August 2026

UPD: Подняли, если что-то не так с сетью - пишите в тикеты my.vdsok.guru или @vdsok_support.

2 May 2026, 12:09 UTC589 views4 reactionsread 8 August 2026

Уважаемые клиенты! Мы знаем о проблеме и уже занимаемся решением. Произошел сбой электропитания в дата-центре ММТС-9, нас переключили на ИБП. Поднимаем сеть. Если у вас есть вопросы - пишите в тикеты my.vdsok.guru или @vdsok_support. С уважением, команда VDSok.guru

custom 54449371960018280474

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

“VDSok.guru” (@vdsokguru), 570 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/vdsokguru.

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.