Channel
@tgx_android_translate
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,840subscribers
+5 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001284170244 |
|---|---|
| Type | Channel |
| Username | @tgx_android_translate |
| Created | 20 August 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/tgx_android_translate |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 22:13 | 1,840 | +4 |
| 9 Aug 2026, 15:32 | 1,836 | +1 |
| 6 Aug 2026, 06:49 | 1,835 | no change |
| 5 Aug 2026, 22:18 | 1,835 | first reading |
20 posts held, back to 29 August 2018 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 2 May 2019. An engagement rate over an empty window would be a number about nothing.
Telegram X Localizations pinned «Starting Telegram X version 0.21.7.1151 cloud localizations are fully supported. You can now create your own localizations for Telegram X on Translations Platform and use links like these to share them with others: https://translations.telegram.org/en/android_x…»
Starting Telegram X version 0.21.7.1151 cloud localizations are fully supported. You can now create your own localizations for Telegram X on Translations Platform and use links like these to share them with others: https://translations.telegram.org/en/android_x https://t.me/setlanguage/zh-hans-beta https://t.me/setlanguage/zh-hant-beta In-app tools for creating translations files will remain. Old localization file…
If you are unable to install localization file or share it as XML, ensure you have translated required strings: language_code language_name language_nameInEnglish language_dateFormatLocale language_continueInLanguage language_continueInLanguagePopupText
0.21.0.992 RC - Separated passcode error messages by type: See PasscodeMismatch*, `PasscodeInvalid*`strings. - Fixed: Can't install localization files with \ in strings (e.g. needed by json_ChatDemo). - New strings used in the pop-up when opening application folder when sending files - Probably fixed: garbage symbols in json_1_* default strings (when translation is missing) on some devices
0.21.0.990 RC - Added NoDocumentsToShowInChat - Fixed: "Settings > Interface > Sticker Suggestions by emoji > Disabled" uses MarkdownDisabled key, although there is SuggestStickersNone key.
Updated: Added lang field description.
To simplify chat demo translations, a lot of new keys have been added in 0.21.0.989. If you don't want to change the scene and want to just translate texts / names, you can set json_ChatDemo to 0 & just translate other json_* strings. If you have already successfuly translated json_ChatDemo, you can keep it as is and don't translate separate strings, but if you don't modify the scene itself, I'd recommend setting j…
New default json_ChatDemo value, which is used, when it's empty (0) or contains invalid JSON.
Note: app won't recommend to switch to your language until language_continueInLanguage, language_continueInLanguagePopupText, language_appliedLanguage are translated.
Built-in value of the json_ChatDemo. You can use JSON minifier to minify the value after translation.
Translators, please check your languages for common typos, before your languages will get released for all users on production (which is about to happen very soon): 1. Tap "View Strings" on built-in language (English) and search for " " (single space character). See what strings start or end with a space and check if your translation has ones as well. On older app version same could be achieved by creating an empty…
0.21.0.988 RC - "View Strings" for built-in language as well for translators (requires access to at least one -raw translation). - Fixed: Invalid rule applied when selecting first item. Affects: *Suffix strings - Added strings needed for language switch pop-up. See https://translations.telegram.org/en/android_x/new - Added json_ChatDemo: array of Scene objects in JSON format. Scene fields on_date: array of integer.…
Showing the 12 most recent of 20 posts we hold for @tgx_android_translate. 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 — 1,054,482 of 1,350,102entries 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 2 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Telegram X Localizations” (@tgx_android_translate), 1,840 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/tgx_android_translate.
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.