—через маты , вылеты из приложения, несколько перезагрузок телефона я смог сделать видео 🙏🏻 конечно со взломом визуал другой , более светлый ,но я все ещё над ним работаю. ★тык на видео★ #repostℳ𝓢 #videoℳ𝓢
Signed パン
![Telegram profile photo for [РЕСТ] 𝙷𝙰𝚁𝚄𝙽𝙾𝙰𝙼𝙴 𝙻𝙸𝙵𝙴 𝙲𝙷𝙰𝙽𝙽𝙴𝙻](https://cdn.tgregister.com/av/66/66d1622b9aa91a2cf24bd9a5e808a7fa9e5d17f3a984056a726d81fd6a775e94.jpg)
Channel
@harunoamelife
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
11subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002248742460 |
|---|---|
| Type | Channel |
| Username | @harunoamelife |
| Description | 🎍инфо: @harunoameflood 🎍влд: @wtxsmy |
| Created | Between 1 May 2024 and 25 August 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/harunoamelife |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 08:16 | 11 | no change |
| 11 Aug 2026, 22:01 | 11 | first reading |
20 posts held, back to 25 August 2024 — 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 20 posts for this entry, the most recent from 21 April 2025. An engagement rate over an empty window would be a number about nothing.
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.
Measured directly from 7 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.
8 reactions across 2 posts, in 5 distinct kinds. The most used accounts for 37.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5208725509529160448 | 3 | 37.5% | |
| 🔥 | 2 | 25.0% | |
| ❤ | 1 | 12.5% | |
| 🍓 | 1 | 12.5% | |
| 🕊 | 1 | 12.5% |
Custom emoji. One 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 count beside it is Telegram’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 2 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 8 reactions 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 25 August 2024 to 21 April 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.
—через маты , вылеты из приложения, несколько перезагрузок телефона я смог сделать видео 🙏🏻 конечно со взломом визуал другой , более светлый ,но я все ещё над ним работаю. ★тык на видео★ #repostℳ𝓢 #videoℳ𝓢
Signed パン
—всех с праздником, а вот и старое новое видео. ★тык на видео★ #repostℳ𝓢 #videoℳ𝓢
Signed パン
🤩𝄄✨✨✨✨✨✨✨✨ ✨✨✨✨✨✨✨𝄄🤩 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩𝄄𝄄Сегодня Селестия снизошла с небес, дабы провести великую чистку, но её сердце было тяжким, а взгляд — омрачённым. Светлая улыбка, некогда озарявшая её лик, исчезла, словно укрытая тучами скорби. В её очах плясали огни разочарования, и, не колеблясь, великая владычица возложила кару на множество звёзд, чьё сияние померкло под тяжестью вины. Над небесным сводом разлилось злове…
Signed パン
。。。🤩⌗ 𝗠𝗔𝗚𝗠𝗔 Сегодня ночью огонь правосудия зажегся вновь, нас покинули Владимир Кризалис Вадим Дракон Ролевая по майору грому (и детсад бабл) ищут новых ролевиков и админов! Ознакомиться с... Списком персонажей Сюжетом Написать по поводу вступления! Администрация #репосто𝘷𝘦
Signed パン
—новое видео от Владика❤️🔥❤️🔥 ★тык на видео★ #repostℳ𝓢 #videoℳ𝓢
Signed パン
—Капитоша молодчина ,новое видео. ★тык на видео★ #videoℳ𝓢 #repostℳ𝓢
Signed варё. сланцыжуй.
—видео от Капитано!! Эффекты от меня🤏🏻🤏🏻 ★тык на видео★ #videoℳ𝓢 #repostℳ𝓢
Signed варё. сланцыжуй.
—новое видео , я конечно не художник,но по трендам все равно хочу. ★Тык на видео★ #videoℳ𝓢 #repostℳ𝓢
Signed варё. сланцыжуй.
—а вот и новое видео !! Немного ленивое, извините. И уж слишком ярко наверное.. ★Тык на видео ★ #videoℳ𝓢 #repostℳ𝓢
Signed варё. сланцыжуй.
✫༻☾𝓝𝓔𝓦 𝓤𝓝𝓘𝓞𝓝☽༺✫ — В этот дивный день своды небес разверзлись, и из их лазурных глубин снизошёл благословенный дар — союз с harunoame flood. Это не просто слияние судеб, но великая песнь, сотканная из шелестящих звёздных троп, переливов таинственных грёз и чарующих шёпотов теней. ✶✶✶ Сама Селестия, в своём незримом величии, простирает над нами крылья света, благословляя этот союз, дабы он был крепок…
🔥2❤1🍓1🕊1
Signed варё. сланцыжуй.
🌱-#Haitam опять уходим в рест. я вообще сейчас не тяну проект...слишком тяжело мне и совсем сил нет. буду набираться короче, надеюсь я быстренько приду в форму. простите. репостов будет мало, союзы не заключаем, в чистках и интерактивах не участвуем. #важноHF #репост
custom 52087255095291604483
Signed варё #варвар |🎧| #сланцыжуй
━━━━━━ 𝗖𝗟𝗘𝗔𝗡𝗜𝗡𝗚 𝗥𝗘𝗦𝗨𝗟𝗧 ━━━━━━ на сегодняшней чистке нас покинули: ☆ Скарамучча ★ Райден ☆Фокалорс набор в чат открыт, в нашем инфо канале Вы можете ознакомиться с правилами,а также списком персонажей. для вступления писать: @eastiy @ioyoooou #𝒓𝒆𝒑𝒐𝒔𝒕_𝑳𝑮
Signed варё #варвар |🎧| #сланцыжуй
Showing the 12 most recent of 20 posts we hold for @harunoamelife. 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.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@harunoamelife named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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.
“[РЕСТ] 𝙷𝙰𝚁𝚄𝙽𝙾𝙰𝙼𝙴 𝙻𝙸𝙵𝙴 𝙲𝙷𝙰𝙽𝙽𝙴𝙻” (@harunoamelife), 11 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/harunoamelife.
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.