Telegram RegisterThe public register of Telegram
Telegram profile photo for Aurora OSS

Channel

Aurora OSS

@AuroraOfficial

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

9,604subscribers

+50 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001184516242
TypeChannel
Username@AuroraOfficial
DescriptionWelcome to AuroraOSS Stable Release Channel. Join our groups for any help & suggestions • Aurora Store group @AuroraSupport • AuroraOSS discussion group @AuroraOSS
Created8 April 2018 — measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live20 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 20 November 2026
On Telegramt.me/AuroraOfficial

Topic

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.

Growth

9,5539,6089,580.56 August 2026 — 9,554 subscribers6 August 2026 — 9,553 subscribers9 August 2026 — 9,576 subscribers12 August 2026 — 9,582 subscribers16 August 2026 — 9,588 subscribers19 August 2026 — 9,589 subscribers23 August 2026 — 9,586 subscribers26 August 2026 — 9,588 subscribers29 August 2026 — 9,589 subscribers1 September 2026 — 9,601 subscribers5 September 2026 — 9,608 subscribers10 September 2026 — 9,603 subscribers14 September 2026 — 9,602 subscribers18 September 2026 — 9,597 subscribers27 September 2026 — 9,583 subscribers5 October 2026 — 9,568 subscribers12 October 2026 — 9,561 subscribers15 October 2026 — 9,565 subscribers17 October 2026 — 9,575 subscribers21 October 2026 — 9,572 subscribers23 October 2026 — 9,579 subscribers26 October 2026 — 9,589 subscribers29 October 2026 — 9,584 subscribers2 November 2026 — 9,571 subscribers5 November 2026 — 9,576 subscribers7 November 2026 — 9,587 subscribers15 November 2026 — 9,591 subscribers20 November 2026 — 9,604 subscribers9,6046 August 202620 November 2026
28 measurements spanning 107 days, net +50. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 9,545–9,616 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
20 Nov 2026, 19:489,604+13
15 Nov 2026, 22:149,591+4
7 Nov 2026, 14:109,587+11
5 Nov 2026, 00:399,576+5
2 Nov 2026, 04:569,571-13
29 Oct 2026, 20:099,584-5
26 Oct 2026, 16:109,589+10
23 Oct 2026, 21:349,579+7
21 Oct 2026, 04:379,572-3
17 Oct 2026, 18:599,575+10
15 Oct 2026, 02:079,565+4
12 Oct 2026, 02:229,561-7
5 Oct 2026, 14:419,568-15
27 Sept 2026, 17:379,583-14
18 Sept 2026, 11:399,597-5
14 Sept 2026, 03:409,602-1
10 Sept 2026, 17:389,603-5
5 Sept 2026, 19:219,608+7
1 Sept 2026, 10:569,601+12
29 Aug 2026, 15:249,589first reading

Engagement

22 posts held, back to 2 July 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 72 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
60.3%
avg views ÷ 9,604 subscribers
Avg views / post
5,790
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 22 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 November 2026
Posts held22 (2 July 2021 – 15 November 2026)
Views total5,790
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Nov 2026, 06:09 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Links
5

Lifetime counters from Telegram’s own channel header, read 22 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Nov 2026, 23:18 UTC≈5,790 viewsread 22 November 2026
File

Changelog: 4.8.5 RC • Added support for delta updates + apk frosting verification • Warning for updates requesting new permissions & trackers • Permissions grouped by category with newly added ones marked • Show Play listings and developer replies on reviews • Storage check before downloads + option to reclaim old/pending installs • Silent updates on Android 17+, cancellable installs • Support for all Shizuku variant…

7 Aug 2026, 21:08 UTC≈16,600 viewsread 22 November 2026
File

Changelog : v2.0.1 * Rewritten from scratch, the UI is now Jetpack Compose and Material 3 * New install methods: session, native, root and Shizuku * Repository sync, downloads and update checks now run as background work * Reworked notifications, with grouped summaries for batch updates * Reworked update checks & more

27 Jul 2026, 17:56 UTC≈22,900 viewsread 22 November 2026
File

Changelog : v4.8.4 (76) • Rebuilt the interface with modern Jetpack Compose • Support for multiple Google accounts • User reviews on the app details screen • Optional app lock via biometrics or device credentials • One-click install for favourites and a buy flow for paid apps • Reworked notifications with grouped summaries and settings • Revamped updates screen; self-updates now shown in the list • More reliable down…

13 May 2026, 15:50 UTC≈20,800 viewsread 22 November 2026
File

Changelog : v4.8.3 (75) • Update microG version • Improve app install state handling • Minor bug fixes and UI/UX improvements • Translation updates

16 Feb 2026, 16:16 UTC≈27,600 viewsread 22 November 2026
File

Changelog : v4.8.1 (73) • Fix login issues • Minor bug fixes and improvements • Translation updates

19 Aug 2025, 08:27 UTC≈44,700 viewsread 22 November 2026
File

Changelog : v4.7.5 (71) • Fix app install issue on huawei devices • Translation updates

28 Jul 2025, 07:13 UTC≈36,000 viewsread 22 November 2026
File

Changelog : v4.7.4 (70) • Do not prompt for microG installs on non-huawei builds • Translation updates

11 Jun 2025, 06:18 UTC≈37,300 viewsread 22 November 2026
File

Changelog : v4.7.2 (68) • Switch to new APIs for searching and installing apps • Search filter is no longer available due to API changes, will be added back later • Fix crash on navigating to app details page • Fix crash on spoofing locale • Translation updates

19 Mar 2025, 05:31 UTC≈41,700 viewsread 22 November 2026
File

Changelog : v4.7.0 (66) • New app compatibility ratings powered by Plexus • Improvements to blacklist manager • Ability to change auto-update restrictions • Minor bug fixes and improvements • Translation updates; additional strings localized

10 Jan 2025, 06:20 UTC≈43,600 viewsread 22 November 2026
File

Changelog : v4.6.4 (65) • Fixed issues with shared library installation for apps like Chrome and WebView • Support for login into personal account using microG • Fixed an issue with auth verification • Translation updates; Additional strings localized

23 Dec 2024, 13:50 UTC≈31,500 viewsread 22 November 2026
File

Changelog : v4.6.3 (64) • Support for archiving/un-archiving apps on Android 15+ • Support for installing apps into private space on Android 15+ • UI adjustments for edge-to-edge support • Multiple bug fixes and improvements • Improvements to notification channels and notifications • Translation updates; Additional strings localized

30 Sept 2024, 09:12 UTC≈31,500 viewsread 22 November 2026
File

Changelog : v4.6.2 (63) • Fixed minor migration issue • Added auto update for Nightly builds • Translation updates

Showing the 12 most recent of 22 posts we hold for @AuroraOfficial. 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.

Forward network

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.

Mentions

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.

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 20 November 2026 — this entry's latest reading, not the date you are reading this.

“Aurora OSS” (@AuroraOfficial), 9,604 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/AuroraOfficial.

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.