Channel
@minezmods
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
479subscribers
+3 since we began measuring on 1 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001935962063 |
|---|---|
| Type | Channel |
| Username | @minezmods |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 October 2026 |
| Last confirmed live | 27 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 27 October 2026 |
| On Telegram | t.me/minezmods |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 27 October 2026 and assigned it the closest of 31 fixed categories, at 86% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Oct 2026, 22:27 | 479 | -1 |
| 14 Oct 2026, 04:11 | 480 | +2 |
| 6 Oct 2026, 02:37 | 478 | +2 |
| 1 Oct 2026, 17:22 | 476 | no change |
| 1 Oct 2026, 16:47 | 476 | first reading |
11 posts held, back to 20 April 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 11 posts for this entry, the most recent from 30 April 2026. An engagement rate over an empty window would be a number about nothing.
54 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 53.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 29 | 53.7% | |
| 👎 | 14 | 25.9% | |
| custom 5377809374016192785 | 11 | 20.4% |
Custom emoji. One 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 count beside it is Telegram’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 8 of the 11 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 54 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 20 April 2025 to 30 April 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.
2023 год, современная война Стороны Русско-сербское войско (РФ+Сербия) Выдуманная славянская страна на балканах (северогорье) У северогорья и у Сербии долго была спорная территория, но Сербия решила завоевать ее при поддержке РФ. Весной началось наступление. Действия Велисово(северогорье) Сюда послали элитную бригаду ВДВ, чтобы отвоевать велисово у ВСС ВСС-вооруженные силы северогорья сервер полностью готов, нам ну…
Signed kadzumasa
Скэбоб
👎7👍4custom 53778093740161927854
то, с чего все начиналось
👍10👎3custom 53778093740161927853
Signed балбес
все новости по серверу будут там
Signed ^
все кто будет играть на сервере заходите сюда https://t.me/minewarjava
Signed ^
————————————————————————————— О ФРАКЦИЯХ: Всего есть 3 фракции которые отличаются своей экипировкой и вооружением за каждую сторону, это: - Мобилизованные(∞ чел.) - Спецура(3 отделения по 10 чел.) - ЧВК(10 чел.) Во всех фракциях(пока что кроме ЧВК) есть свои классы: - Штурмовик - Пулеметчик - Снайпер - Гранатометчик(Мобилизованные) / Разведчик(Спецура) Все классы отличаются своим уникальным вооружением ————————…
custom 53778093740161927853
Signed ^
рф
👍5
Signed ^
если что щас такая снаряга
👎4👍1
Signed ^
меняем на такую снарягу?
👍2
Signed ^
пездо
👍3custom 53778093740161927851
Signed ^
чиго
👍4
Signed ^
Showing the 11 most recent of 11 posts we hold for @minezmods. 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.
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.
@minezmods named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 27 October 2026 — this entry's latest reading, not the date you are reading this.
“Business prod. - Minecraft” (@minezmods), 479 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/minezmods.
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.