Channel
@apexxports
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
466subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002381991834 |
|---|---|
| Type | Channel |
| Username | @apexxports |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/apexxports |
Gaming — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 05:21 | 466 | -1 |
| 27 Aug 2026, 22:14 | 467 | -2 |
| 21 Aug 2026, 02:03 | 469 | +2 |
| 14 Aug 2026, 19:38 | 467 | -1 |
| 6 Aug 2026, 19:03 | 468 | no change |
| 6 Aug 2026, 14:18 | 468 | first reading |
20 posts held, back to 17 March 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 31 July 2026. An engagement rate over an empty window would be a number about nothing.
This month marks one year since I started porting ROMs. I want to thank everyone who has supported me throughout this journey. I've met amazing people, learned so much from friends and other porters, and tried to help others whenever I could. There have been ups and downs, but I never stopped loving what I do. I won't be coming back. Instead, I've decided to focus on working on myself. I don't want to be the versio…
Signed apex ?
I was never a good dev, was I ? I never contributed to anything and my ports have always been buggy because I didn't put enough effort in them. I failed as both a porter and a person. I was always rude to everyone and I'm deeply sorry for that. I act childish, making jokes that are unfunny and sometimes too deep. I'm sorry for everything.
Signed apex ?
Sharvil is at it again 🤣
Signed apex ?
Happy Easter!
Signed apex ?
#ruby #hyperos3 #android16 #PORT ❗ HyperOS 3 Android 16 (FINAL) 📲 Redmi Note 12 Pro/+/Discovery 5G (rubyx) 📱 Ported from: Xiaomi 14T Pro (rothko) ‼️ Bugs: - NFC 📝 Notes: - FASTBOOT ROM - SELinux Permissive - Added new wallpapers - AOD works - Stock camera was replaced with a fixed one, but it may have some bugs since it's still in development. Another camera app was added to ensure no user problems with the repla…
Signed apex ?
Bluetooth fixed! Thanks @mr_mishun
Signed apex ?
I don't know how to fix Bluetooth. The ROM will probably not be released
Signed apex ?
Full changelogs: - added a new wallpaper - fixed a bug with wallpapers - fixed brightness
Signed apex ?
Brightness bug fixed!
Signed apex ?
Currently testing fix, will come soon
Signed apex ?
But again, the port works fine
Signed apex ?
Sorry for the inconvenience everyone!!! The port works fine and can be flashed without any issues, but I did realize that it's not running on stock kernel because I forgot to change the boot image to the stock one 😭
Signed apex ?
Showing the 12 most recent of 20 posts we hold for @apexxports. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Apex's Stuff” (@apexxports), 466 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/apexxports.
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.