Telegram RegisterThe public register of Telegram
Telegram profile photo for Minecraft-Hosting.net - Защищенный Игровой Хостинг

Channel

Minecraft-Hosting.net - Защищенный Игровой Хостинг

@spaceroute

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

3,964subscribers

-18 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001753917142
TypeChannel
Username@spaceroute
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/spaceroute

Topic

Gaming — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@spaceroute/301 · this entry30 Jun 2026, 18:19 UTC@minecraftrent/15530 Jun 2026, 18:20 UTC1.00under a minute
@spaceroute/303 · this entry6 Jul 2026, 10:09 UTC@minecraftrent/1576 Jul 2026, 10:10 UTC1.00under a minute
@spaceroute/304 · this entry8 Jul 2026, 16:53 UTC@minecraftrent/1588 Jul 2026, 16:53 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@minecraftrent7 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (6–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 10 comparable posts for this entry, running 30 June 2026 to 3 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @spaceroute — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

3,9634,0604,011.57 August 2026 — 3,982 subscribers7 August 2026 — 3,982 subscribers8 August 2026 — 3,983 subscribers10 August 2026 — 4,007 subscribers14 August 2026 — 4,025 subscribers17 August 2026 — 4,047 subscribers20 August 2026 — 4,053 subscribers24 August 2026 — 4,060 subscribers27 August 2026 — 4,036 subscribers30 August 2026 — 4,042 subscribers2 September 2026 — 4,040 subscribers6 September 2026 — 4,041 subscribers11 September 2026 — 4,011 subscribers15 September 2026 — 3,992 subscribers27 September 2026 — 3,981 subscribers5 October 2026 — 3,963 subscribers12 October 2026 — 3,964 subscribers3,9647 August 202612 October 2026
17 measurements spanning 66 days, net -18. 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 3,948–4,075 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 09:023,964+1
5 Oct 2026, 11:403,963-18
27 Sept 2026, 19:193,981-11
15 Sept 2026, 07:563,992-19
11 Sept 2026, 10:164,011-30
6 Sept 2026, 11:574,041+1
2 Sept 2026, 11:084,040-2
30 Aug 2026, 08:154,042+6
27 Aug 2026, 13:384,036-24
24 Aug 2026, 12:234,060+7
20 Aug 2026, 22:234,053+6
17 Aug 2026, 18:474,047+22
14 Aug 2026, 05:084,025+18
10 Aug 2026, 20:464,007+24
8 Aug 2026, 07:203,983+1
7 Aug 2026, 19:323,982no change
7 Aug 2026, 19:123,982first reading

Engagement

10 posts held, back to 30 June 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 2 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

35 reactions across 8 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤35100.0%

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

Measured over the 10 most recent posts we hold, published 30 June 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.

Recent posts

3 Aug 2026, 17:15 UTC361 views6 reactionsread 8 August 2026

🚀 Два обновления в панели ⚡️ Апгрейд тарифа в один клик Взяли сервер на линейке ЭКО, чтобы протестировать, и упёрлись в мощность? Теперь можно перейти на любой тариф категории выше - например, с ЭКО на МОЩНЫЙ. Без переносов вручную и без обращения в поддержку. 🌍 Смена локации сервера Ошиблись со страной при заказе - не беда. Сменить локацию можно самостоятельно, в пару кликов. 📍 Где найти: «Мои серверы» → нужный с…

❤6

31 Jul 2026, 08:50 UTC662 views4 reactionsread 8 August 2026

На ноде 066 изменился цифровой айпи адрес на 213.171.18.154. Старый айпи скоро будет отключен. Выдайте игрокам новый айпи и если есть домен, то не забудьте изменить DNS запись. Причина смены - подключение защиты от DDoS Guard (на других нодах она уже подключена и аналогичных процедур не ожидается).

❤4

19 Jul 2026, 09:11 UTC≈1,170 views7 reactionsread 8 August 2026
Forwarded from @mineguard_networkPhoto

В очередной раз выпускаем крупное обновление. Быть владельцем сервера стало ещё проще, а защита умнее и совершенее. Список игроков и их пинг Теперь прямо в панели видно, кто сейчас на сервере: ник, пинг в реальном времени и точку входа, через которую игрок к вам подключается. Пинг подсвечивается цветом, поэтому проблемные подключения заметны сразу. Рядом медиана пинга по всем игрокам, чтобы одним взглядом понять, ка…

❤7

16 Jul 2026, 15:26 UTC908 views5 reactionsread 8 August 2026

⚠️ На нодах 124, 125, 126 также пройдут внеплановые работы 16.07 в 19:00 по МСК, в результате которых сменится цифровой IP адрес и порты. Работы продлятся несколько часов. Если вы не хотите ждать завершения работ, то можете написать в поддержку уже сейчас и работы на вашем сервере проведут досрочно, всего за несколько минут.

❤5

15 Jul 2026, 17:35 UTC999 viewsread 8 August 2026

⚠️ 16 июля в 15:00 по МСК на нодах 045, 048, 108, 113 пройдут технические работы в результате которых у серверов сменится цифровой IP адрес и порты. Работы продлятся несколько часов. Если вы не хотите ждать завершения работ, то можете написать в поддержку уже сейчас и работы на вашем сервере проведут досрочно, всего за несколько минут.

11 Jul 2026, 10:07 UTC969 views5 reactionsread 8 August 2026
Forwarded from @nlauncherPhoto

❤️NLauncher вышел в релиз. Рассказываем, что мы вообще сделали Долгое время мы делали лаунчер, которым хотели бы пользоваться сами. Без рекламы на пол-экрана, без установки в нагрузку левых программ, без вечного «скачайте наш браузер». Сегодня открываем его для всех. Коротко: это бесплатный лаунчер Minecraft, который весит 7 мегабайт, ставится за минуту и дальше просто не мешает играть. Обновляется сам, в фоне, вы э…

❤5

11 Jul 2026, 08:05 UTC775 views2 reactionsread 8 August 2026
Forwarded from @mineguard_networkPhoto

🛡 Глобальное обновление защиты Мы выпустили самую долгожданную и революционную функцию в мире облачных защит - внутриигровую проверку на бота. Вам больше не нужно включать веб-капчу, теперь игрок сможет пройти проверку прямо внутри Minecraft. На выбор есть 2 защиты: звуковая и интерактивная. 🔊 В звуковой игроку нужно по звуку определить моба и написать номер цифры, под которой он находится. Проверка сделана максима…

❤2

8 Jul 2026, 16:53 UTC680 views2 reactionsread 8 August 2026

Сегодня в 22:00 по МСК на 134 ноде будут работы, которые ориентировочно продлятся 2 часа. Будет усилено охлаждение и добавлено ОЗУ.

❤2

6 Jul 2026, 10:09 UTC940 views4 reactionsread 8 August 2026

Дорогие клиенты! Внедрение новой защиты на всех узлах завершено ✅ Теперь корректная работа сервисов зависит от того, какой тип порта выбран во вкладке «Сеть». Если тип указан неверно, трафик будет отфильтрован и сервис перестанет отвечать. Проверьте, что для каждого порта выбран правильный тип: 🎮 Minecraft Java для игрового сервера (Java) 🧱 Bedrock для Bedrock-сервера или для Geyser 🎧 Voice chat для PlasmoVoice / …

❤4

30 Jun 2026, 18:19 UTC≈1,140 viewsread 8 August 2026

Дорогие клиенты! Мы обновили ECO линейку тарифов и добавили туда Amd Epyc 7713. Этот процессор по мощности эквивалентен Amd Ryzen 9 3950X. Процессоры на ECO линейке теперь такие: Intel Xeon 6148 (2075 Single Thread Rating) Amd Epyc 7713 (2647 Single Thread Rating) Все серверы на ECO тарифах расположены в Москве, это отличные тарифы для старта вашего проекта или для организации тестовых серверов.

Showing the 10 most recent of 10 posts we hold for @spaceroute. 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

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.

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

“Minecraft-Hosting.net - Защищенный Игровой Хостинг” (@spaceroute), 3,964 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/spaceroute.

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.