5 Aug 2024, 06:32 UTC≈1,580 viewsread 11 August 2026
Current github organizations: github.com/s5e8825 github.com/s5e8535
Channel
KrutosX Bio
@KrutosX
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
32subscribers
+0 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 | -1001664350897 |
|---|---|
| Type | Channel |
| Username | @KrutosX |
| Description | Just my bio. Anything else?... |
| Created | 31 December 2021 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/KrutosX |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 02:01 | 32 | no change |
| 8 Aug 2026, 00:36 | 32 | first reading |
Engagement
11 posts held, back to 31 December 2021 — 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 11 posts for this entry, the most recent from 5 August 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 4
Lifetime counters from Telegram’s own channel header, read 11 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.
Recent posts
5 Aug 2024, 06:28 UTC≈1,520 viewsread 11 August 2026
] Announcement We are expanding, and since July 4, I own main 1280 channel! @Exy1280_updates - Channel @Exy1280_dis - Discussion And welcome to Exynos 1330: @exy1330 - Channel @Exynos1330 - Discussion
24 Feb 2024, 14:07 UTC≈1,760 viewsread 11 August 2026
] Announcement! New channel and chat for Redmi Note 11 projects under the hood of DragonFox Team (@KrutosX and @TotallyNotJinx) are here! > @dragonfox_spes | Main channel > @dragonfox_spes_chat | Chat for those
10 Dec 2023, 10:35 UTC≈1,860 viewsread 11 August 2026
] Announcement! New chat for Tecno MT6768/6769 projects under the hood of DragonFox Team (@KrutosX and @TotallyNotJinx) is here! > @tecnomt6768 | Main chat
1 Sept 2023, 07:55 UTC≈1,970 viewsread 11 August 2026
] Announcement! New channel and chat for Exynos 9611 projects under the hood of DragonFox Team (@KrutosX and @TotallyNotJinx) are here! > @dragonfoxxo | Main channel > @dragonfoxchat | Chat for those
23 Jul 2023, 10:23 UTC≈2,000 viewsread 11 August 2026
] Announcement! New public chat for Exynos 1280 development (Galaxy A53, A33, M33 and M34) is here! > @exy1280 | Main chat
15 May 2023, 10:45 UTC≈2,160 viewsread 11 August 2026
] Announcement! New channel and chat for my projects! > @kru_upd | Updates > @armv9a | Chat
18 Nov 2022, 04:22 UTC≈2,620 viewsread 11 August 2026
------ One important message! If you have any of old Samsung SC8830 devices, like Galaxy Tab E 9.6, Galaxy Tab 3 Lite VE, Galaxy Grand Prime VE, Galaxy Core Prime or any others, which have Android 4.4.4 out of box with TouchWiz, and are ready to test or develop for this SoC platform, please PM me, I need you! If you will feel better, you can write message to sc8830 group instead https://t.me/sc8830 Thank you! -----…
31 Dec 2021, 21:31 UTC≈2,840 viewsread 11 August 2026
---- Github: https://github.com/KrutosVIP Telegram: @krutosx Dev Logs (RU): @kosxdev Kuroneko Development: @Kuroneko_Updates UniversalX: @universalgsi UniversalX Links: @universalxandroid Discord: krutosx (KrutosX#3599) Feel free to pm me, if you rly need some help from me. ---- Also check out my friend's/etc channels/groups! Asriel : @asrieldashiebio @Asrielbackyard Enderxity: @xityBio Danila222/danya227: @danya227…
31 Dec 2021, 21:28 UTC≈2,660 viewsread 11 August 2026
Hello, I am KrutosX (he/him), or Kru for my friends, middle Android dev and maintainer from Russia. Languages: Russian (native) | English | Spanish (a little) Also, I like to code on Python, C/C++ and Java/Kotlin. My favorite system is Linux (Basically, Android for its architecture, Arch for its purity and Debian for good optimization) You can see me on XDA and 4PDA. Currently, I only learning to build some stuff, …
31 Dec 2021, 21:10 UTCviews —
Channel created
Showing the 11 most recent of 11 posts we hold for @KrutosX. 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 — 522,346 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.
Mentions
Named by 5 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.
asrieldashie's self introduction
@asrieldashiebio · 61 postDragonFox Development (spes/spen)
@dragonfox_spes · 621 postDragonFox Development (Exynos 9611)
@dragonfoxxo · 1411 postExynos 1280 Updates
@Exy1280_updates · 1,1151 postExynos 1330 Updates
@Exy1330 · 2081 postKru's Updates
@kru_upd · 151 post[MAIN] KNXD Development
@Kuroneko_Updates · 441 postUniversalX Hub
@universalxandroid · 401 post
@asrieldashiebio · 61 postDragonFox Development (spes/spen)
@dragonfox_spes · 621 postDragonFox Development (Exynos 9611)
@dragonfoxxo · 1411 postExynos 1280 Updates
@Exy1280_updates · 1,1151 postExynos 1330 Updates
@Exy1330 · 2081 postKru's Updates
@kru_upd · 151 post[MAIN] KNXD Development
@Kuroneko_Updates · 441 postUniversalX Hub
@universalxandroid · 401 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“KrutosX Bio” (@KrutosX), 32 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/KrutosX.
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.