Channel name was changed to «𝙉𝙖𝙝𝙞𝙙𝙖 𝙙𝙖𝙞𝙡𝙮 (Рест)»

Channel
𝙉𝙖𝙝𝙞𝙙𝙖 𝙙𝙖𝙞𝙡𝙮 (Рест)
@Hahida_daily_genshin
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
180subscribers
-39 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003845915379 |
|---|---|
| Type | Channel |
| Username | @Hahida_daily_genshin |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/Hahida_daily_genshin |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 95% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 16:48 | 180 | -2 |
| 4 Nov 2026, 04:17 | 182 | -4 |
| 28 Oct 2026, 05:15 | 186 | -4 |
| 21 Oct 2026, 02:11 | 190 | -3 |
| 13 Oct 2026, 08:16 | 193 | -6 |
| 3 Oct 2026, 19:40 | 199 | -3 |
| 19 Sept 2026, 05:35 | 202 | -2 |
| 9 Sept 2026, 22:22 | 204 | -4 |
| 1 Sept 2026, 04:26 | 208 | -5 |
| 25 Aug 2026, 03:36 | 213 | -3 |
| 16 Aug 2026, 20:48 | 216 | -3 |
| 8 Aug 2026, 10:34 | 219 | no change |
| 7 Aug 2026, 19:23 | 219 | first reading |
Engagement
20 posts held, back to 1 August 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 11s
- Average length
- 11s
Measured directly from 1 video 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
62 reactions across 12 posts, in 9 distinct kinds. The most used accounts for 17.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5422624703460173276 | 11 | 17.7% | |
| custom 5379675326852921638 | 9 | 14.5% | |
| custom 5258397265868902693 | 8 | 12.9% | |
| custom 5278292074075019925 | 8 | 12.9% | |
| custom 5258488611233354052 | 7 | 11.3% | |
| custom 5276182480628505633 | 7 | 11.3% | |
| custom 5424671117937768521 | 6 | 9.68% | |
| custom 5318935014589625239 | 4 | 6.45% | |
| 🕊 | 2 | 3.23% |
Custom emoji. 8 of the rows above are 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 are 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 12 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 62 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 1 August 2026 to 6 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
Здравствуйте,к сожалению беру рест до 29 августа,простите что так долго
🕊2custom 52782920740750199251
Signed #кʏсᴀчкᴀ
☺️☺️☺️𝓝𝓪𝓱𝓲𝓭𝓪 𝓭𝓪𝓲𝓵𝔂 ︎︎︵͡ ִ۫ 🩷 ┆︎#Hahida #art #newpost☺️ ︎ ︎ ︎ ︎ ︎︎ ︎ ︎ ︎ ︎︎ ︎ ︎ ︎𓈒︎ 𝑐𝑟: @srn_111 𝑜𝑛 ︎x
custom 53796753268529216385custom 54226247034601732761custom 54246711179377685211
Signed #кʏсᴀчкᴀ
☺️☺️☺️𝓝𝓪𝓱𝓲𝓭𝓪 𝓭𝓪𝓲𝓵𝔂 ︎︎︵͡ ִ۫ 🩷 ┆︎#Hahida #art #newpost☺️ ︎ ︎ ︎ ︎ ︎︎ ︎ ︎ ︎ ︎︎ ︎ ︎ ︎𓈒︎ 𝑐𝑟: @toro_yztro 𝑜𝑛 ︎x
custom 54226247034601732762custom 53796753268529216381custom 54246711179377685211
Signed #кʏсᴀчкᴀ
ᅠ𝗪𝗘𝗟𝗖𝗢𝗠𝗘 𝗧𝗢 𝗗ׄA𝗜𝗟𝗬 𝗠𝗔𝗙𝗨𝗬𝗨 📻 ⁝ любите асахину мафую ? хотелось бы ежедневно видеть контент с ней, а также поделиться собственным ? ➡️ тогда мы спешим пригласить именно тебя в наш замечательный канал ! 🍫
Signed #кʏсᴀчкᴀ
╭─────────────── • ╰─ ʚ new pꪮst ɞ (⚡) Админ: Ultimate ‧₊ ෧ 🌱 ༅. 🍃 .𓏲࣪ ✨ ✩ .𝑐𝑟𝑒𝑑𝑖𝑡::twit ⠀ ⠀ … Boost #Hahida_daily #New_post
custom 52583972658689026932custom 54226247034601732762custom 52761824806285056331
Signed Ultimate Kyouko... FrickCHADFurinaАрхонтЭстралюбСаньхуяHertaСкиркСиельАкихаНияColum
⭐🎀 hey🏁are you there? 🎀🐋ㅤ 🔇elcome to… ㅤㅤ🤩🤩🤩🤩🤩🤩🤩🤩🤩🔇 ➿➿➿ㅤ 🎀🩵🎀 ㅤ* Приветствуем ВАС в сети каналов RUNADELTA по видеоигре Deltarune (и её ау) 🎀 ㅤ* Здесь вы сможете наблюдать за жизнью персонажей или даже взять на себя роль одного из них! ㅤ* Мы рады каждому !! 🏁 🎀🥹🥹 ㅤ 🏁🅰️авигация для вас🏁
Signed #кʏсᴀчкᴀ
>File name:Hometown_Social_Network Status:downloaded Opening process... Success< ──────────────────────────── Социальная сеть Hometown.com приветствует вас! ʾʿ 𓈒ִ 𝆺𝅥 .ʿ 𝅄 ׁ ⭔︩ׄ . 𝂅 ࣪𝆬 . ʾ 𖧧 ׄ ʾ 𓈒ִ 𝆭 ࣳ ࿚ ִ 𞥊 ⋮ 𖥻 𓈒ִ 𝆹𝅥 ⋆ Вы стремитесь отыграть роль любимого персонажа? ⋆ Или желаете увидеть, как он проводит свои обычные деньки? ⋆ А может хотите заполнить несколько интерактивов? 𐔌 ִ ⏜ ꯭ ๋ ۶ৎ ⫶ 🍪༢ …
Signed #кʏсᴀчкᴀ
☺️☺️☺️𝓝𝓪𝓱𝓲𝓭𝓪 𝓭𝓪𝓲𝓵𝔂 ︎︎︵͡ ִ۫ 🩷 ┆︎#Hahida #art #newpost☺️ ︎ ︎ ︎ ︎ ︎︎ ︎ ︎ ︎ ︎︎ ︎ ︎ ︎𓈒︎ 𝑐𝑟: @HUCA2DOG 𝑜𝑛 ︎x
custom 52761824806285056332custom 53189350145896252392custom 54226247034601732761
Signed #кʏсᴀчкᴀ
☺️☺️☺️𝓝𝓪𝓱𝓲𝓭𝓪 𝓭𝓪𝓲𝓵𝔂 ︎︎︵͡ ִ۫ 🩷 ┆︎#Hahida #art #newpost☺️ ︎ ︎ ︎ ︎ ︎︎ ︎ ︎ ︎ ︎︎ ︎ ︎ ︎𓈒︎ 𝑐𝑟: @sus1_ro 𝑜𝑛 ︎x
custom 52584886112333540523custom 52782920740750199252custom 53796753268529216381
Signed #кʏсᴀчкᴀ
🎀🔤arbara cf х daily 🤩🤩 👻👻⛪⛪⛪⛪⛪⛪ 🤩тебе понравилась девушка с церкви Фавония, но ищешь везде по ней контент и не можешь его найти⁉️🤩🤩🤩 👻👻👻👻👻👻👻👻👻👻 🥹🥹welcome to Barbara cf x daily 🥹🎇
Signed #кʏсᴀчкᴀ
☺️☺️☺️𝓝𝓪𝓱𝓲𝓭𝓪 𝓭𝓪𝓲𝓵𝔂 ︎︎︵͡ ִ۫ 🩷 ┆︎#Hahida #art #newpost☺️ ︎ ︎ ︎ ︎ ︎︎ ︎ ︎ ︎ ︎︎ ︎ ︎ ︎𓈒︎ 𝑐𝑟: @Dodosaae 𝑜𝑛 ︎x
custom 52584886112333540522custom 54226247034601732762custom 53189350145896252391
Signed #кʏсᴀчкᴀ
Showing the 12 most recent of 20 posts we hold for @Hahida_daily_genshin. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
Names
Channels on the register whose handles appear in this channel's posts.
@angelnicolereeyn · 1131 post[ТЕХ.РАБОТЫ] ˖𝖫𝗂𝗀𝗁𝗍𝖲𝗈𝗎𝗅.𝗇𝖾𝗍 - сетка [по Дельтарун
@deltarunesetka2 · 811 postᅠ𝗱𝗮𝗶𝗹𝘆𝗠𝗔𝗙𝗨𝗬𝗨
@mafuyudaily · 4381 post-✧᥉tιᥴkᥱr᥉ ᥕιth ᥲᥒ𐔤 𐔥ᥲᥒᦔ𐔖ⲙ᥉! 🌙/ᥴⲧυⲕᥱρы ᥴ ᥈юⳝыⲙυ ⲫᥲⲏⲇ𐔖ⲙᥲⲙυ оᴛ нᴀɯих ᴀдʍиноʙ!!🌙✧-
@stikeru_ot_mikoko · 3581 postwww_hometown_com
@www_HomeTown_com · 41 post
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“𝙉𝙖𝙝𝙞𝙙𝙖 𝙙𝙖𝙞𝙡𝙮 (Рест)” (@Hahida_daily_genshin), 180 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/Hahida_daily_genshin.
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.