Telegram RegisterThe public register of Telegram
Telegram profile photo for Аρ᥊ᥙʙ Д᧐ʙᥱρᥙя/𐌿ρ᧐ʙᥱρκᥙ

Channel

Аρ᥊ᥙʙ Д᧐ʙᥱρᥙя/𐌿ρ᧐ʙᥱρκᥙ

@trustarhiv

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

32subscribers

-4 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003507138125
TypeChannel
Username@trustarhiv
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live25 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/trustarhiv

Growth

32363411 August 2026 — 36 subscribers12 August 2026 — 36 subscribers19 August 2026 — 35 subscribers25 September 2026 — 32 subscribers11 August 202625 September 2026
4 measurements spanning 45 days, net -4. 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 31–37 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 14:2232-3
19 Aug 2026, 00:4635-1
12 Aug 2026, 08:3336no change
11 Aug 2026, 17:3136first reading

Engagement

7 posts held, back to 14 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 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 7 posts for this entry, the most recent from 17 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

9 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 88.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤888.9%
💘111.1%

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

Measured over the 7 most recent posts we hold, published 14 June 2026 to 17 June 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

17 Jun 2026, 16:34 UTC76 views2 reactionsread 11 August 2026

Сап, на связи #noname проверила бот "ночная тишь" (@tvoihearts_bot) 1. Оформление бота: в тгк бота все ссылки правила есть 10/10 2. Приветствие админа: Меня никто не взял( 0/10 3.оформление бота: В описание бота есть ссылки на ткг, отзывы и тег влд на анкету ссылки нет( 9/10 4. Тег админа: Мне никто не ответил( 0/10 5. Комфорт во время общения: Мне не оказали поддержку( 0/10 6. Название бота: "Ночная тишь"- и п…

❤2

Signed no name

15 Jun 2026, 15:40 UTC108 views3 reactionsread 11 August 2026

Салам всем, я #лиссерл проверил бот "@devills contract" (@devillscontract_Bot) 1. Оформление бота В тгк бота, все имеется и все посты самые главные. Есть поздраляющий пост про начало лето, это достаточно. 10/10 2. Приветствие админа. В приветствие админа имеется ссылка на тгк, на отзывы и про информацию, про смене админа. 10/10 3. Оформление бота В описании бота имеется ссылка на тгк, на отзывы и на бот анкет. Все…

❤2💘1

Signed lisserl0rallomero ۫

15 Jun 2026, 15:39 UTC80 viewsread 11 August 2026
Photo

Photo, posted without a caption

Signed lisserl0rallomero ۫

15 Jun 2026, 11:43 UTC98 viewsread 11 August 2026
Photo

Photo, posted without a caption

Signed 𝙎𝙝𝙞𝙛𝙧 #𝙰𝚃 #tortik

15 Jun 2026, 11:43 UTC87 views4 reactionsread 11 August 2026

Ну чтож , новый день , новый разъеб. Ебитесь , дети мои. С вами #шифр и сегодня мы оценим "дружный" коллектив бота "Небесный дождь" Начнем с того , что там самый "ахуенный" владелец со своими ебейшими правилами , я оставлю вам скрин. Наш владелец #бог — он действительно возомнил себя богом и постоянно истерил что его никто не слушается , вместо того , что бы прекратить ссору , он продолжал орать на своих админов , …

❤4

Signed 𝙎𝙝𝙞𝙛𝙧 #𝙰𝚃 #tortik

14 Jun 2026, 23:18 UTC86 views0 reactionsread 11 August 2026

Здравствуйте, на связи #лиссерл и проверил бот "ангел хранитель" ( @guardian_angel777_Bot ) 1. Оформление тгк В тгк бот находиться самое главное, нету разных интерактивных постов. Так нормально, но что-то не хватает. 9/10 2. Приветствие админа. Ну.. в приветствии нету ссылки на тгк, на отзывы , но есть информация, что пз может поменять админа. Это радует. 4/10 3. Оформление бота В описании бота нечего не указано..…

Signed lisserl0rallomero ۫

14 Jun 2026, 23:15 UTC69 viewsread 11 August 2026
Photo

Photo, posted without a caption

Signed lisserl0rallomero ۫

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

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Аρ᥊ᥙʙ Д᧐ʙᥱρᥙя/𐌿ρ᧐ʙᥱρκᥙ” (@trustarhiv), 32 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/trustarhiv.

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.