Channel
@MokeeDownloads
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
673subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001314465545 |
|---|---|
| Type | Channel |
| Username | @MokeeDownloads |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/MokeeDownloads |
Technology — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 |
|---|---|---|
| 11 Sept 2026, 21:38 | 673 | +2 |
| 3 Sept 2026, 00:34 | 671 | -1 |
| 26 Aug 2026, 15:02 | 672 | +1 |
| 18 Aug 2026, 20:53 | 671 | -2 |
| 12 Aug 2026, 21:56 | 673 | -1 |
| 6 Aug 2026, 16:39 | 674 | no change |
| 6 Aug 2026, 10:57 | 674 | first reading |
20 posts held, back to 6 January 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 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 January 2023. An engagement rate over an empty window would be a number about nothing.
New MokeeOS build is out! Device: Motorola G5S Codename: #montana Type: Nightly Android: 11.0 FileSize: 775.04 MB BuildDate: 2023-01-06 11:31:21 MD5: 6c0a796ce122d77e703b77cfc92157d9 Filename: MK110.1-montana-202301061043-NIGHTLY.zip Download: Click here @MokeeDownloads
New MokeeOS build is out! Device: OnePlus 7T Codename: #hotdogb Type: Nightly Android: 11.0 FileSize: 844.13 MB BuildDate: 2023-01-06 11:32:17 MD5: 04c52e3556f42616660341c6d4b0478c Filename: MK110.1-hotdogb-202301061103-NIGHTLY.zip Download: Click here @MokeeDownloads
New MokeeOS build is out! Device: Sony Xperia XA2 Plus Codename: #voyager Type: Nightly Android: 11.0 FileSize: 734.71 MB BuildDate: 2023-01-06 12:01:06 MD5: 1ac67e0872a014c389b312cac350e3fc Filename: MK110.1-voyager-202301061115-NIGHTLY.zip Download: Click here @MokeeDownloads
New MokeeOS build is out! Device: OnePlus 8 Codename: #instantnoodle Type: Nightly Android: 11.0 FileSize: 1.05 GB BuildDate: 2023-01-06 12:21:38 MD5: 5ba07773648ae79c27872cbdc246b427 Filename: MK110.1-instantnoodle-202301061130-NIGHTLY.zip Download: Click here @MokeeDownloads
New MokeeOS build is out! Device: Motorola Z2 Force Codename: #nash Type: Nightly Android: 11.0 FileSize: 854.63 MB BuildDate: 2023-01-06 12:41:15 MD5: 4d22e8b6409175efd5b233f8be758ed0 Filename: MK110.1-nash-202301061208-NIGHTLY.zip Download: Click here @MokeeDownloads
New MokeeOS build is out! Device: Xiaomi 6X Codename: #wayne Maintainer: @PIPIPIG233666 Type: Nightly Android: 11.0 FileSize: 824.06 MB BuildDate: 2023-01-06 12:51:19 MD5: a559c3f330a151410e382626960b0d9c Filename: MK110.1-wayne-202301061159-NIGHTLY.zip Download: Click here @MokeeDownloads
New MokeeOS build is out! Device: OnePlus 8 Pro Codename: #instantnoodlep Type: Nightly Android: 11.0 FileSize: 1.07 GB BuildDate: 2023-01-06 12:52:37 MD5: 7bad011b14beeb80f6a77673d9f21a7d Filename: MK110.1-instantnoodlep-202301061213-NIGHTLY.zip Download: Click here @MokeeDownloads
New MokeeOS build is out! Device: Redmi Note 5 Codename: #whyred Maintainer: @guaiyihu Type: Nightly Android: 11.0 FileSize: 829.42 MB BuildDate: 2023-01-06 13:11:14 MD5: e9c5dd5dd1952e4d26eca97ab1b217ee Filename: MK110.1-whyred-202301061243-NIGHTLY.zip Download: Click here @MokeeDownloads
New MokeeOS build is out! Device: Lenovo P2 (P2a42 Intl) Codename: #kuntao Type: Nightly Android: 11.0 FileSize: 751.65 MB BuildDate: 2023-01-06 13:21:06 MD5: a2567b39801bfc84d80a5b0c20b20579 Filename: MK110.1-kuntao-202301061307-NIGHTLY.zip Download: Click here @MokeeDownloads
New MokeeOS build is out! Device: Motorola X4 Codename: #payton Type: Nightly Android: 11.0 FileSize: 745.66 MB BuildDate: 2023-01-06 13:31:05 MD5: 13e5edc91365585d6c51a74d3c61afca Filename: MK110.1-payton-202301061239-NIGHTLY.zip Download: Click here @MokeeDownloads
New MokeeOS build is out! Device: Motorola Edge Codename: #racer Type: Nightly Android: 11.0 FileSize: 784.4 MB BuildDate: 2023-01-06 14:21:55 MD5: 24d9309fabdc411b9edfcf12d72ff4c6 Filename: MK110.1-racer-202301061327-NIGHTLY.zip Download: Click here @MokeeDownloads
New MokeeOS build is out! Device: Motorola E5 Plus Codename: #rhannah Type: Nightly Android: 11.0 FileSize: 773.16 MB BuildDate: 2023-01-06 15:01:27 MD5: 3d974c9fa2a91a0f9eab56fa6d8f208c Filename: MK110.1-rhannah-202301061413-NIGHTLY.zip Download: Click here @MokeeDownloads
Showing the 12 most recent of 20 posts we hold for @MokeeDownloads. 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 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@MokeeDownloads named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“MokeeOS” (@MokeeDownloads), 673 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/MokeeDownloads.
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.