Telegram RegisterThe public register of Telegram
Telegram profile photo for ShardVPN | Канал

Channel

ShardVPN | Канал

@ShardVPN

On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry

34,843subscribers

+6,497 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002854586315
TypeChannel
Username@ShardVPN
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/ShardVPN

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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 why it has no browse page of its own yet.

Growth

28,34634,84331,594.57 August 2026 — 28,346 subscribers8 August 2026 — 28,517 subscribers8 August 2026 — 28,878 subscribers9 August 2026 — 29,001 subscribers10 August 2026 — 29,067 subscribers11 August 2026 — 29,163 subscribers12 August 2026 — 29,671 subscribers13 August 2026 — 30,081 subscribers14 August 2026 — 30,309 subscribers16 August 2026 — 30,404 subscribers17 August 2026 — 30,971 subscribers18 August 2026 — 31,126 subscribers19 August 2026 — 31,170 subscribers20 August 2026 — 31,327 subscribers21 August 2026 — 31,454 subscribers23 August 2026 — 31,783 subscribers25 August 2026 — 31,920 subscribers26 August 2026 — 32,164 subscribers27 August 2026 — 32,354 subscribers27 August 2026 — 32,472 subscribers28 August 2026 — 32,498 subscribers29 August 2026 — 32,544 subscribers30 August 2026 — 32,658 subscribers31 August 2026 — 32,703 subscribers1 September 2026 — 32,772 subscribers2 September 2026 — 32,877 subscribers4 September 2026 — 33,091 subscribers6 September 2026 — 33,372 subscribers9 September 2026 — 33,535 subscribers12 September 2026 — 33,651 subscribers14 September 2026 — 33,816 subscribers15 September 2026 — 34,843 subscribers7 August 202615 September 2026
32 measurements spanning 39 days, net +6,497. 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 27,371–35,818 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
15 Sept 2026, 19:1734,843+1,027
14 Sept 2026, 01:3933,816+165
12 Sept 2026, 05:5533,651+116
9 Sept 2026, 21:0033,535+163
6 Sept 2026, 15:3833,372+281
4 Sept 2026, 07:3833,091+214
2 Sept 2026, 17:4232,877+105
1 Sept 2026, 18:5732,772+69
31 Aug 2026, 16:0832,703+45
30 Aug 2026, 14:1532,658+114
29 Aug 2026, 17:4732,544+46
28 Aug 2026, 18:0732,498+26
27 Aug 2026, 21:3832,472+118
27 Aug 2026, 00:0532,354+190
26 Aug 2026, 03:2432,164+244
25 Aug 2026, 00:3731,920+137
23 Aug 2026, 11:0531,783+329
21 Aug 2026, 20:2831,454+127
20 Aug 2026, 16:2331,327+157
19 Aug 2026, 15:3631,170first reading

Engagement

30 posts held, back to 5 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 67 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
28.4%
avg views ÷ 34,843 subscribers
Avg views / post
9,900
3 posts measured
Reaction rate
0.36%
reactions ÷ views · ER floor
Posts in window
3
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
WindowRolling 30 days · latest post in window 7 September 2026
Posts held30 (5 June 20267 September 2026)
Views total29,710
Reactions total107
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Sept 2026, 14:47 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

1,107 reactions across 30 posts, in 8 distinct kinds. The most used accounts for 64.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
71164.2%
👾12411.2%
🎉988.85%
🔥867.77%
😭484.34%
😢181.63%
😴161.45%
🍓60.542%

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 1,107 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 5 June 2026 to 7 September 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

7 Sept 2026, 20:43 UTC≈3,410 views31 reactionsread 9 September 2026

Сейчас плотно работает РКН 😢 Сейчас стоят у нас рабочие и не рабочие локации, уже нашли решение и начинаем его внедрять. Проверяйте пинг в приложении, там будут стоят рабочие и подключайтесь к ним. Если есть другие вопросы, обращайтесь в поддержку: @ShardSupport_bot Решили ✅

22🔥9

24 Aug 2026, 18:45 UTC≈11,800 views40 reactionsread 9 September 2026

Нам важно ваше мнение ❤️ Что нам сделать, чтобы вы с удовольствием советовали Shard VPN своим друзьям и знакомым? Чего вам сейчас не хватает? Какие функции или возможности вы хотели бы видеть у нас? Пишите всё как есть - идеи, пожелания и даже критику. Мы всё читаем и хотим развивать Shard VPN вместе с вами ❤️ Комментарии открыл 🫶

26🔥14

18 Aug 2026, 17:45 UTC≈14,500 views36 reactionsread 9 September 2026

⚠️ Проблема на операторе связи в Москве, ММТС-9 упал Из-за этого легла половина российского интернета, в том числе некоторые наши сервера. Часть серверов работает, обход 2 также работает! Ожидаем восстановления... 💃 UPD: Все восстановили!

24🔥12

15 Aug 2026, 22:50 UTC≈13,800 views31 reactionsread 9 September 2026

🏴 Закончили тех.работы обновите подписку в приложении 🎁 Промокод: SORRY 2 дня бесплатного обхода! Действует до конца 16 августа 👾 UPD: Промокод - ВСЕ (((

🔥2011

15 Aug 2026, 20:13 UTC≈11,600 views17 reactionsread 9 September 2026

Начали тех.работы над обходами

🔥125

15 Aug 2026, 17:00 UTC≈11,400 views34 reactionsread 9 September 2026

🔥Что произошло сегодня?👇 Сегодня во Франкфурте произошла крупная авария, из-за которой возникли проблемы с интернет-связью. Все наши серверы работают, но местами могут быть перебои: повышенный пинг, разрывы соединения и нестабильная скорость. Проблема массовая — затронут не только НАШ VPN, но и многие другие VPN-сервисы и интернет-провайдеры. 🌙 Сегодня ночью начнём работы, чтобы не мешать пользователям, и постара

24🔥10

15 Aug 2026, 12:42 UTC≈8,900 views24 reactionsread 9 September 2026

🎁 Компенсация за сбой В качестве компенсации за сегодняшний массовый сбой дарим 2 дня Обхода бесплатно. Промокод: SORRY Активировать: @shard_vpnbot → «Аккаунт» → «Промокод» → SORRY

20🔥4

15 Aug 2026, 12:02 UTC≈9,260 views17 reactionsread 9 September 2026
Photo

⚡️Обходы снова работают! Сбой был массовым — проблемы были практически у всех VPN-сервисов. Сейчас всё восстановили. Обновите подписку в приложении 🔄 Сегодня добавим ещё обычные локации 🏴

12🔥5

15 Aug 2026, 09:09 UTC≈8,720 views34 reactionsread 9 September 2026

⚠️ Сейчас наблюдаются проблемы с обходами и частью серверов. Уже решаем проблему 🛠️ Сообщим, как только всё восстановим. ✍️ Поддержка: @Shardsupport_bot

😭277

12 Aug 2026, 19:46 UTC≈11,400 views78 reactionsread 9 September 2026

3️⃣0️⃣0️⃣0️⃣0️⃣ 💃

🎉4533

24 Jul 2026, 17:10 UTC≈20,600 views48 reactionsread 9 September 2026

🎁 Раздаём бесплатные дни VPN! Забирай промокод RUSS 🎁 ⚡ 2 дня бесплатного обхода для всех. Можешь поделиться промокодом с друзьями — пусть тоже попробуют. Как активировать: @shard_vpnbot → «Аккаунт» → «Промокод» → введите RUSS 🟢UPD: Промокод истек

35🎉13

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

Posts edited after publishing

@ShardVPN edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
17 August 2026
Most recent edit
9 September 2026

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

18 Jul 2026, 19:14 UTCAnonymous Poll477 voters

Голосуйте в опросе ниже 👇

  1. 👍 Да, бесплатные дни лучше62%
  2. 💰 Лучше оставить выплаты деньгами (В USDT)27%
  3. 🤷 Всё равно, буду пользоваться любым вариантом22%

The shares total 111%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 30 most recent posts we hold, published 5 June 2026 to 7 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“ShardVPN | Канал” (@ShardVPN), 34,843 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/ShardVPN.

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.