Channel
@NekogramX
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
55,654subscribers
-3,003 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001305127566 |
|---|---|
| Type | Channel |
| Username | @NekogramX |
| Description | The official channel of the NekogramX messenger. Apks: @NekoXApks CI Builds: @NekoX_CI |
| Created | 25 February 2020 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/NekogramX |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 13:36 | 55,654 | -28 |
| 9 Nov 2026, 00:00 | 55,682 | -54 |
| 7 Nov 2026, 13:20 | 55,736 | -19 |
| 6 Nov 2026, 15:54 | 55,755 | -21 |
| 5 Nov 2026, 16:00 | 55,776 | -38 |
| 4 Nov 2026, 16:57 | 55,814 | -30 |
| 3 Nov 2026, 18:10 | 55,844 | -38 |
| 2 Nov 2026, 14:59 | 55,882 | -8 |
| 1 Nov 2026, 15:25 | 55,890 | -39 |
| 31 Oct 2026, 11:56 | 55,929 | -38 |
| 30 Oct 2026, 15:28 | 55,967 | -24 |
| 29 Oct 2026, 13:41 | 55,991 | -52 |
| 28 Oct 2026, 10:37 | 56,043 | -32 |
| 27 Oct 2026, 11:59 | 56,075 | -24 |
| 26 Oct 2026, 13:54 | 56,099 | -33 |
| 25 Oct 2026, 12:06 | 56,132 | -23 |
| 24 Oct 2026, 14:06 | 56,155 | -43 |
| 23 Oct 2026, 14:27 | 56,198 | -25 |
| 22 Oct 2026, 17:46 | 56,223 | -38 |
| 21 Oct 2026, 16:17 | 56,261 | first reading |
20 posts held, back to 20 January 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 195 pages 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 17 June 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 November 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.
#RELEASE 9.5.8 - merge official 9.5.8 - remove the proxy functionalities - bug fixes Long time no see! We developers are getting back to continue maintaining NekoX. We will release 9.7.6 soon and catch up the official updates as soon as possible. If you are interested in helping us testing, please join @NekoX_CI . GitHub Release | Apks | Check Update
#RELEASE 9.3.3 * Merge official 9.3.3 * Allow using Telegram API as a translator * Bug fixes and Improvements GitHub Release | Apks | Check Update
#RELEASE 9.1.6 * Merge official 9.1.6 * Fix noGcm varieties Long time no see! NekoX is not deprecated even though we are very slow to track upstream updates. The latest version 9.3.3 is testing, please wait! Happy Lunar New Year! GitHub Release | Apks | Check Update
#PRE_RELEASE 8.9.3-preview01 * Merge official 8.9.3 * Use Google Maps in release builds * Update Apple emoji pack * Bug fixes and improvements This is a preview version and may contains unknown bugs. noGcm builds are delayed, please checkout comments for reason. Since NekoX 8.9.3, we end support for devices below Android 4.4 (API 19) GitHub Release | Apks | Check Update
#RELEASE 8.8.5-rc02 * Bug fixes and improvements GitHub Release | Apks | Check Update
#RELEASE 8.8.5-rc01 * Option to disable premium sticker animations * Refactor Neko Settings * Bug fixes GitHub Release | Apks | Check Update
#PRE_RELEASE 8.8.5-preview05 * Merge official 8.8.5 * Bug fixes This is a preview version and may contain unknown bugs. Please update at your own risk. GitHub Release | Apks | Check Update
#RELEASE 8.7.4 * Bug fixes GitHub Release | Apks | Check Update
#PRE_RELEASE 8.7.4-preview01 * Merge upstream 8.7.4 * Bug fixes GitHub Release | Apks | Check Update
#RELEASE 8.6.2 * Bug fixes GitHub Release | Apks | Check Update
#RELEASE 8.6.2-rc01 * Merge upstream 8.6.2 GitHub Release | Apks | Check Update
#RELEASE 8.6.1-preview02 * Bug fixes GitHub Release | Apks | Check Update
Showing the 12 most recent of 20 posts we hold for @NekogramX. 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.
Named by 33 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 30 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“NekoX Updates” (@NekogramX), 55,654 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/NekogramX.
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.