Telegram RegisterThe public register of Telegram

Channel

TGuard — правда слишком неудобна.

@TGuard_Truth

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

18subscribers

+0 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002964937522
TypeChannel
Username@TGuard_Truth
CreatedBetween 1 August 2025 and 3 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/TGuard_Truth

Growth

188 August 2026 — 18 subscribers11 August 2026 — 18 subscribers8 August 202611 August 2026
2 measurements spanning 3 days. 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 17–19 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 18:3118no change
8 Aug 2026, 10:0118first reading

Engagement

16 posts held, back to 3 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 16 posts for this entry, the most recent from 9 October 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
8
Videos
2
Links
4

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
1m 17s
Average length
39s

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.

Recent posts

9 Oct 2025, 07:04 UTC765 viewsread 11 August 2026
Photo

Человек, который пиарит бота, говорит, что он сломает канал 😁

8 Oct 2025, 20:08 UTC667 viewsread 11 August 2026
Photo

На канале, где пиарили бота для защиты от накрутки... накрутили подписчиков Кажется — что за анекдот? Но это реальность. Всего минут за 10 на канал накрутили более 2000 человек, но бот видимо равняется на стандарты дна вирта и среагирует часов через 11 😎 В целом, удобно — вот вам в рекламном канале сразу же демонстрация (не)работы бота 🤩 Как я понимаю, защита от рейдерства аналогичная дну вирта. Это сильно. ☺️ Уд

4 Oct 2025, 10:37 UTC≈2,460 viewsread 11 August 2026

Не забываем подписываться на наш блог, там осветим ещё больше фактов. Все только начинается 😌 — https://t.me/UtopianTake

4 Oct 2025, 10:29 UTC≈2,420 viewsread 11 August 2026
Forwarded from @RaidGuard

Меня крайне занимает избирательность вашей «критики». Вы с легкостью отвергаете многосоставные доказательства, подменяя анализ примитивными мантрами: «Архитектор сказал» или «На скриншотах нет ID». Позвольте спросить: если, по вашей же логике, в оригинальном клиенте iOS 26 можно якобы подделать юзернейм, то что мешает подделать и ID, и дату установки аватарки? Ваша позиция лишена внутренней целостности и является обр

4 Oct 2025, 09:49 UTC≈3,120 viewsread 11 August 2026

Забавно наблюдать, как они пытаются оправдаться, мол "На записи не видно ID! А юзернейм можно подделать!". Ребят, вы там упали или что? Записи предоставлены с оригинального клиента iOS, юзернейм невозможно подделать. Нет таких способов.

3 Oct 2025, 21:16 UTC≈3,940 viewsread 11 August 2026

⭐️ Статья с подробным объяснением диалога — https://teletype.in/@raidguard/TGuard_Truth

3 Oct 2025, 21:06 UTC≈3,770 viewsread 11 August 2026

🖼 Скриншоты: — https://t.me/TGuard_Truth/10 — https://t.me/TGuard_Truth/11 — https://t.me/TGuard_Truth/12 — https://t.me/TGuard_Truth/13 📁 Скриншоты файлом: — https://t.me/TGuard_Truth/14 — https://t.me/TGuard_Truth/15 — https://t.me/TGuard_Truth/16 — https://t.me/TGuard_Truth/17 🖼 Запись экрана: — https://t.me/TGuard_Truth/19 📁 Запись экрана файлом: — https://t.me/TGuard_Truth/20 📷 Запись от 3-его лица: — https:

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

Citation-graph rank

Citation-graph rank — 615,679 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

Named by 28 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“TGuard — правда слишком неудобна.” (@TGuard_Truth), 18 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/TGuard_Truth.

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.