Channel
@hikka_ub
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
686subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001679998924 |
|---|---|
| Type | Channel |
| Username | @hikka_ub |
| Description | Ongoing development of the Hikka descendant: lightweight, yet powerful userbot for Telegram. |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/hikka_ub |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 02:30 | 686 | no change |
| 7 Aug 2026, 11:19 | 686 | first reading |
20 posts held, back to 29 October 2023 — 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 25 March 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 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.
860 reactions across 20 posts, in 17 distinct kinds. The most used accounts for 28.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😢 | 241 | 28.0% | |
| ❤🔥 | 124 | 14.4% | |
| ❤ | 73 | 8.49% | |
| 😱 | 73 | 8.49% | |
| 🌚 | 54 | 6.28% | |
| 🎉 | 53 | 6.16% | |
| ☃ | 45 | 5.23% | |
| 🥰 | 39 | 4.53% | |
| 🤩 | 31 | 3.60% | |
| ⚡ | 27 | 3.14% | |
| 🐳 | 25 | 2.91% | |
| 👏 | 24 | 2.79% | |
| 😁 | 23 | 2.67% | |
| 🔥 | 14 | 1.63% | |
| 🎅 | 8 | 0.93% | |
| 🎄 | 3 | 0.349% | |
| 🕊 | 3 | 0.349% |
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 20 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 860reactions 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 29 October 2023 to 25 March 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.
Also, some great news. We have partnered with some yet undisclosed service provider to make deployment of Shinsei easier for non-technical users. Gentle reminder: no official support will be provided. Not in the support chat, not in DMs.
⚡26🐳10🌚8❤🔥3😁3
Signed Daniil Gazizullin
A little under a week after Hikka's 3rd birthday, a new project went into the pre-alpha stage (v0.1.0-a1 Hayai). Currently, 15 brave devs are in the process of scrolling through code and trying to deploy a fresh new Telegram soldier. Some people in the community have already deduced the name of the new project, and I'd like to confirm it. Shinsei. And yes, you guessed the origin of this name precisely right. It is …
❤🔥21❤9🔥5🐳4😢3👏1😁1😱1
Signed Daniil Gazizullin
🫡 Stay tuned
❤🔥35☃8😱7🌚3🔥1
Signed Daniil Gazizullin
Want to say something about Hikka? Maybe want to express your expectations about a new userbot or say a few words to the developer? https://forms.gle/fyM8qd7atuTR1zCr5 I will later give a post or two with QA from this form.
❤8❤🔥4🐳1
Signed Daniil Gazizullin
Announcement for a PBT of the new userbot will be published in this channel after private alpha is finished. A bunch of small insights into the new userbot policy: - There will be no official support provided, only community. - Userbot will not in any way support Termux, UserLand and other non-standard servers. - Modules will not be compatible between Hikka and [new userbot]. Hope this helps
☃21😢7🐳6❤4
Signed Daniil Gazizullin
🫡 As sad as it is, Hikka is officially discontinued. It is now an archived project, which will no longer be maintained, nor will it be updated. Due to multiple complaints on the long-ago-discontinued UnitHeta, it was completely removed from core modules and instead replaced by a side-loaded companion. For my close friends, I will disclose the reasons for this sharp reaction, which has led to project discontinuatio…
😢52❤🔥3🎉3👏1
Signed Daniil Gazizullin
https://forms.gle/ruX8MkyEQRKh2JUy5
🌚13👏4😱1
Signed Daniil Gazizullin
😛 Hi everyone! Got amazing news for ya. I have no time to complete the *100% scam protection* on 1.6.4. (This includes the development, testing and internal bug bounty to check the protection) BUT I can publish new changes from 1.6.4 (includes some basic security checks). This will not include the 100% protection from scam, but will bring some new features and protections to life. This means, that the soon publis…
❤17❤🔥6😱4🌚2🥰2
Signed Daniil Gazizullin
😃 As a substitute for the built-in Heta you can use this module .dlm https://heta.dan.tatar/nheta.py It uses the same database as the original, but works on client side.
❤14❤🔥6🔥4🌚1😱1
Signed Daniil Gazizullin
⚠️ Unit Heta was completely shut down, thus the modules may not be loading as of now. They will be switched to static mode soon, but the bot and search will not be available, unfortunately. I may think of a better solution in the future, but for now — no search.
😢40🎉3😱3😁2☃1👏1
Signed Daniil Gazizullin
I'd like to kindly remind you about the existence of the code licensing. Within Hikka there are certain parts, which are licensed under CC BY NC ND 4.0 license. This means, that you can't edit+redistribute this code. Moreover, you are not allowed to sell the code. If the license violation attempt will be detected, you will be banned in the Hikka community (and other bad things might happen, e.g. lawsuit or account bl…
😱39❤6❤🔥6😁6🌚3🐳3🔥3🕊2
Signed Daniil Gazizullin
As you might have noticed, TLD .ru was (is?) experiencing outage. Please, refer to this guide if you get an error message while installing modules. https://t.me/mintsifry/2114
😱13
Signed Daniil Gazizullin
Showing the 12 most recent of 20 posts we hold for @hikka_ub. 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 — 915,395 of 1,480,688entries 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.
Named by 4 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.
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.
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.
“Shinsei ニュース” (@hikka_ub), 686 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/hikka_ub.
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.