Telegram RegisterThe public register of Telegram

Channel

[РЕСТ] 𝙃𝙀𝙏𝙐𝙊𝙃 𝘿𝙀𝙍𝙏||𝙇𝙄𝙁𝙀

@HTD_life

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

162subscribers

+3 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-1003815695731
TypeChannel
Username@HTD_life
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/HTD_life

Growth

159162160.58 Aug 2026, 11:04 — 159 subscribers8 Aug 2026, 17:31 — 159 subscribers8 Aug 2026, 18:58 — 162 subscribers8 Aug 2026, 11:048 Aug 2026, 18:58
3 measurements taken within a single day, net +3. 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 159–162 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 18:58162+3
8 Aug 2026, 17:31159no change
8 Aug 2026, 11:04159first reading

Engagement

20 posts held, back to 6 August 2026the 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.

ERR · 30 days
26.7%
avg views ÷ 162 subscribers
Avg views / post
43.3
19 posts measured
Reaction rate
5.83%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 3 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held20 (6 August 20268 August 2026)
Views total822
Reactions total7
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 17:31 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.

Reaction mix

7 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5355162273457414636342.9%
custom 5357485099145273507342.9%
custom 5433751726773528049114.3%

Custom emoji. Every 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 counts beside them areTelegram’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 3 of the 20 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 August 2026 to 8 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

8 Aug 2026, 17:19 UTC7 viewsread 8 August 2026

:: Тайлер, а ассоциация #𝙃𝙏𝘿𝙨𝙘𝙝𝙥

8 Aug 2026, 17:13 UTC11 views1 reactionsread 8 August 2026
Photo

✦ 𝗡𝗘𝗪 𝗨𝗡𝗜𝗢𝗡 ✦ « 𝗢𝗻 𝘁𝗵𝗶𝘀 𝗯𝗲𝗮𝘂𝘁𝗶𝗳𝘂𝗹 𝗱𝗮𝘆, 𝘁𝘄𝗼 𝘄𝗮𝗻𝗱𝗲𝗿𝗶𝗻𝗴 𝘀𝗼𝘂𝗹𝘀 𝘂𝗻𝗶𝘁𝗲𝗱, 𝘁𝗵𝗲𝘆 𝗮𝗻𝗰𝗵𝗼𝗿𝗲𝗱 𝘁𝗵𝗲𝗶𝗿 𝘀𝗼𝘂𝗹𝘀 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 𝘁𝗵𝗲 𝗱𝗮𝗿𝗸 𝘄𝗼𝗿𝗹𝗱 ». ━━━━━━━━━━━━━━ 𝗦𝗼... 𝗪𝗶𝘁𝗵 𝗷𝗼𝘆 𝗮𝗻𝗱 𝗵𝗮𝗽𝗽𝗶𝗻𝗲𝘀𝘀, 𝘄𝗲 𝗴𝗿𝗲𝗲𝘁 𝗼𝘂𝗿 𝗮𝗹𝗹𝗶𝗲𝘀 — «𝐕𝐄𝐋𝐕𝐄𝐓 𝐕𝐎𝐈𝐂𝐄𝐒 ִֶָ». 𖥔𝗹𝗶𝗳𝗲 ::@Velvet_Volces_life 𖥔𝗶𝗻𝗳𝗼 ::@Velvet_Volces_info 𖥔𝘁𝗿𝗮𝗰𝗸𝗲𝗿𝗿 ::@Anon_Penel0pe_vvs_bot 𝗜 𝗵𝗼𝗽𝗲 𝘁𝗵𝗮𝘁 𝗼𝘂𝗿 𝗽𝗮𝘁𝗵𝘀 𝘄𝗶𝗹𝗹 𝗯𝗲 𝘁𝗼𝗴𝗲𝘁𝗵𝗲𝗿 𝗳𝗼𝗿 𝗮 𝗰𝗲𝗻𝘁𝘂𝗿𝘆. #𝙎𝙝𝙞𝙣𝙤𝙗𝙮 #𝙃𝙏𝘿𝙪𝙣𝙞𝙤𝙣

custom 53574850991452735071

8 Aug 2026, 16:33 UTC20 viewsread 8 August 2026

Всем пр крч я ваша любимая совлд❤️❤️ и я буду следящим окда? И я ищю союзы активно прям)) писать:: @Hetuoh_bot :: кто тебе админку дал🤔 Ты камон, бож я совлд☠ #𝙎𝙝𝙞𝙣𝙤𝙗𝙮 #March7 #𝙃𝙏𝘿𝙧𝙚𝙥𝙤𝙨𝙩

8 Aug 2026, 12:08 UTCviews —

Channel name was changed to «[РЕСТ] 𝙃𝙀𝙏𝙐𝙊𝙃 𝘿𝙀𝙍𝙏||𝙇𝙄𝙁𝙀»

8 Aug 2026, 12:07 UTC45 views5 reactionsread 8 August 2026

:: ща #𝙃𝙏𝘿𝙨𝙘𝙝𝙥

custom 53551622734574146362custom 53574850991452735072custom 54337517267735280491

8 Aug 2026, 10:48 UTC50 viewsread 8 August 2026
Photo

𝙣𝙚𝙬 𝙪𝙣𝙞𝙤𝙣 «союзы создаются нe случайно — они начинаются с довeрия и взаиmного уважeния.» ━═━═━═━═━═━═━═━═━ спeшиm подeлиться прeкрасной новостью — тeпeрь mы состоиm в союзe с « ɢᴀᴄʜᴀᴠᴇʀs » !! ✦ будem рады поддeрживать друг друга и развиваться вmeстe. обязатeльно заглянитe к ниm: @GachaversLife || @GachaversInfo #𝙃𝙏𝘿𝙪𝙣𝙞𝙤𝙣

8 Aug 2026, 10:29 UTC48 viewsread 8 August 2026
Photo

𝙣𝙚𝙬 𝙪𝙣𝙞𝙤𝙣 «союзы создаются нe случайно — они начинаются с довeрия и взаиmного уважeния.» ━═━═━═━═━═━═━═━═━ Перезаключаем союз с 𝓛𝒆𝒘𝒅𝒏𝒆𝒔𝒔 на семейный! Теперь они нам Пасифика, а мы им Мейбл. #𝙃𝙏𝘿𝙪𝙣𝙞𝙤𝙣

Showing the 12 most recent of 20 posts we hold for @HTD_life. 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 — 12,538 of 1,160,990entries 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

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 17 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.

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

“[РЕСТ] 𝙃𝙀𝙏𝙐𝙊𝙃 𝘿𝙀𝙍𝙏||𝙇𝙄𝙁𝙀” (@HTD_life), 162 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/HTD_life.

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.