Telegram RegisterThe public register of Telegram
Telegram profile photo for Glory to the Heroes

Channel

Glory to the Heroes

@gtth_official

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry

2,436subscribers

+5 since we began measuring on 13 September 2026

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

Register entry

Telegram ID-1001716487413
TypeChannel
Username@gtth_official
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 September 2026
Last confirmed live19 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/gtth_official

Growth

2,4302,4362,43313 September 2026 — 2,431 subscribers15 September 2026 — 2,430 subscribers19 September 2026 — 2,436 subscribers13 September 202619 September 2026
3 measurements spanning 5 days, net +5. 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 2,429–2,437 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 00:372,436+6
15 Sept 2026, 01:222,430-1
13 Sept 2026, 20:222,431first reading

Engagement

8 posts held, back to 25 December 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.

ERR · 30 days
59.9%
avg views ÷ 2,436 subscribers
Avg views / post
1,460
1 post measured
Reaction rate
2.81%
reactions ÷ views · ER floor
Posts in window
1
of 8 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 29 August 2026
Posts held8 (25 December 2025 – 29 August 2026)
Views total1,460
Reactions total41
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Sept 2026, 20:22 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.

What this channel posts

Video runtime
1m 19s
Average length
40s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

388 reactions across 6 posts, in 14 distinct kinds. The most used accounts for 46.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤17946.1%
🔥7419.1%
🥰3910.1%
👍328.25%
❤‍🔥153.87%
🤬153.87%
👎102.58%
🖕71.80%
🆒51.29%
💊51.29%
🫡30.773%
⚡20.515%
🌚10.258%
🤯10.258%

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

Measured over the 8 most recent posts we hold, published 25 December 2025 to 29 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

29 Aug 2026, 12:02 UTC≈1,460 views41 reactionsread 13 September 2026
Photo

Цими вихідними ми проводимо нове закрите публічне тестування Glory to the Heroes - триденний Server Slam, який уже розпочато! Цього разу ми відкриваємо для тестування велике оновлення пре-альфи на вже знайомих мапах Бої за Кринки та Часів Яр - Канал, а також уперше представимо абсолютно нову локацію. Основне в новому білді - оптимізації продуктивності, PvPvE з повноцінним ШІ у PvP, нові формати Contact і Operations…

❤33👎3🫡3💊1🤯1

27 Jun 2026, 12:43 UTC≈4,910 views61 reactionsread 13 September 2026
Photo

Село Кринки та прилеглі території були повністю переосмислені після їхньої останньої появи в PvE, щоб точніше передати реальний прототип 2023 року: щільну сільську забудову, моторошні зруйновані подвір’я, туманні херсонські ліси та заболочені плавні. Разом із переробленими механіками, новими системами, а також значно покращеними візуалом і продуктивністю, це PvP-оновлення виводить рівень занурення у Glory to the Her…

❤44❤‍🔥9👍5🆒2🌚1

27 Jun 2026, 12:40 UTC≈3,710 views44 reactionsread 13 September 2026
Photo

Протягом останніх кількох місяців після завершення останнього публічного плейтесту ми були повністю зосереджені на фундаментальному покращенні гри на основі отриманого фідбеку та продовжували розробку на шляху до раннього доступу. Зараз ми готуємо ґрунт для наступної великої ітерації PvP-тестування. Оновлення повертає повністю перероблену мапу «Бої за Кринки», а також масштабні зміни більшості ігрових систем. Крім т…

❤30❤‍🔥6👍5🆒2🔥1

18 Mar 2026, 14:07 UTC≈8,890 views107 reactionsread 13 September 2026
Photo

Оновлення Steam Playtest - PvP вже доступно! Ми раді оголосити масштабне оновлення - Steam Playtest оновлюється першим PvP-режимом. Він уже доступний! Це закрита початкова фаза PvP-плейтесту, присвячена стрес-тестуванню онлайн-інфраструктури та мультиплеєрних механік. Наразі доступ мають лише гравці з ключем активації Steam Playtest. Що чекає на учасників: - Нова мапа - копія 1:1 мікрорайону Канал Часового Яру, зи…

🥰39👍22❤17🤬15🖕7💊4🔥2🆒1

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

Appears in Telegram’s recommendations for other channels

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.

Arena Breakout: Infinite
@officialarenabreakoutinfinitecis · 49,186
Telegram ranks this channel #40 of 68 here — alongside 67 others — read 13 September 2026

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.

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

“Glory to the Heroes” (@gtth_official), 2,436 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/gtth_official.

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.