-- здравствуйте! мы закрываемся, все союзы разрываются

Channel
愛 : hᥲᤐບ › Ꮏiʑ
@Harutisinf
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
6subscribers
+0 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 | -1002883331822 |
|---|---|
| Type | Channel |
| Username | @Harutisinf |
| Description | 𝖲𝘁𝗮𝗋𝗍 : 𝟤𝟨.𝟢𝟨 . . ᯏ ₊ 𝖮𝗐𝗻.'𝗌 : @na1nat × @trwxx 𝖫𝗶𝗳𝖾 : @harutislf / 𝖡𝗈𝗍 : @harutiss_bot ; -- все нужное находится в навигации . |
| Created | Between 1 June 2025 and 18 June 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Harutisinf |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 21:15 | 6 | no change |
| 11 Aug 2026, 02:45 | 6 | first reading |
Engagement
20 posts held, back to 18 June 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 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 20 posts for this entry, the most recent from 23 July 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 10
- Videos
- 4
- Links
- 2
Lifetime counters from Telegram’s own channel header, read 12 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
- 56s
- Average length
- 14s
Measured directly from 4 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
31 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 25.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5422388905460654519 | 8 | 25.8% | |
| custom 5357357315278253846 | 6 | 19.4% | |
| custom 5253510490734217044 | 4 | 12.9% | |
| custom 5395746922675843122 | 4 | 12.9% | |
| custom 5395322927799349399 | 3 | 9.68% | |
| custom 5451744805065351488 | 3 | 9.68% | |
| custom 5238006492019308936 | 2 | 6.45% | |
| custom 5395477336168619608 | 1 | 3.23% |
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 10 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 31reactions 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 18 June 2025 to 23 July 2025, 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
· --- 𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎 --- · 𝒜 𝗎𝗍𝗁𝗈𝗋 : Sua. 𝖨𝖽ꫀ𝖺 : dk. 𝗍ꫀ𝗑𝗍 : нас срочно надо нью. #𝗏𝗂𝖽𝖾𝗈_𝖧Ͳ𝖲
custom 54223889054606545192custom 53573573152782538461
· --- 𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎 --- · 𝒜 𝗎𝗍𝗁𝗈𝗋 : Sua. 𝖨𝖽ꫀ𝖺 : dk. 𝗍ꫀ𝗑𝗍 : так и живём #𝗏𝗂𝖽𝖾𝗈_𝖧Ͳ𝖲
Sticker, posted without a caption
Sticker, posted without a caption
· --- 𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎 --- · 𝒜 𝗎𝗍𝗁𝗈𝗋 : Sua. 𝖨𝖽ꫀ𝖺 : dk. 𝗍ꫀ𝗑𝗍 : .... #𝗏𝗂𝖽𝖾𝗈_𝖧Ͳ𝖲
Sticker, posted without a caption
custom 53953229277993493991
· --- 𝐍𝐄𝐖 𝐕𝐈𝐃𝐄𝐎 --- · 𝒜 𝗎𝗍𝗁𝗈𝗋 : Sua. 𝖨𝖽ꫀ𝖺 : dk. 𝗍ꫀ𝗑𝗍 : так и живём #𝗏𝗂𝖽𝖾𝗈_𝖧Ͳ𝖲
custom 52535104907342170441custom 53573573152782538461custom 53957469226758431221custom 54223889054606545191custom 54517448050653514881
Sticker, posted without a caption
. 🤩 «🎀» 𝗈𝗌𝗍 𝗋𝗈 . 𝗅𝖾 𝖼𝗁𝖺𝗇𝗀𝖾 ; 🤎 ———— 𝐃ля того, что бы поменять роль, нужно заполнить анкету и отправить сюда ! . | 1.— Старая роль : | 2.— Новая роль : | 3. — Фандом : | 4. — Ваш юз : 🤩
custom 54223889054606545192custom 52380064920193089361custom 53573573152782538461
Sticker, posted without a caption
↷ 🥰 `« 🤩 » - 𝗈𝗌𝗍 . 𝗌𝖾𝗍 ; @𝗇𝖺1𝗇𝖺𝗍 -------------- 𝐒𝐇 . 𝖻𝗅𝗈𝗇𝖾 анкеты для вступления во флуд. Анкету заполните строго по шаблону, текст кликабельный. После отправки анкеты подайте заявку на вступление в чат. [ ссылка для отправления заявки. ] 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 「𝟙. Фото персонажа: 𝟚. Имя персонажа: 𝟛. Фандом: 𝟜. Юз человека: 」 °• Правила обязательны для 💋 вступления во флуд, незнание правил не о…
custom 52535104907342170442custom 53954773361686196081custom 53957469226758431221
Showing the 12 most recent of 20 posts we hold for @Harutisinf. 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 — 1,409,916 of 1,478,351entries 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 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.
Handles this channel named that no longer answer
- Dead references
- 4
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 4
- vacant every time we have ever looked
@Harutisinf named 4 handles 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“愛 : hᥲᤐບ › Ꮏiʑ” (@Harutisinf), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Harutisinf.
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.