Tomorrow, Saturday, July 4th, the entire Drauger OS network will experience intermittent downtime as all servers receive yearly scheduled maintenance. We appreciate your patience as we work to keep our systems secure and running smoothly.

Channel
Drauger OS News
@draugeros_news
On this record: Topic · Growth · Engagement · Posts · Polls · Cite this entry
39subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001198517297 |
|---|---|
| Type | Channel |
| Username | @draugeros_news |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 7 October 2026 |
| On Telegram | t.me/draugeros_news |
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 30 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 21:56 | 39 | -1 |
| 10 Aug 2026, 19:16 | 40 | no change |
| 7 Aug 2026, 20:57 | 40 | first reading |
Engagement
20 posts held, back to 23 July 2024 — 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 4 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
I am proud to announce the stable release of Drauger OS 7.8, codename Urgal! This release comes with a number of features and changes over 7.7: Kernel 7.0 Drauger OS 7.8 ships with kernel 7.0 out of the box, meaning immediate support from day one of NTSYNC, meaning much improved performance over Drauger OS 7.7 at launch. KDE Plasma 6.5 We've upgraded to Plasma 6.5, this comes with a number of creature comforts, in…
Happy Star Wars Day, everyone! May the 4th be with you! For those who are unaware, today is also Drauger OS's 8th birthday! Drauger OS was originally released back in 2018 with the Xfce desktop, and was intended as an emulation station of sorts. Over time, Drauger OS has grown, matured, and expanded it's aim. Now, we're one of the longest running gaming distros on the market. Thanks for making the past 8 years a b…
Drauger OS 7.8, Beta 3, Codenamed Urgal, is now available! This is another iterative update. At this point, we expect the stable release to ship with at least kernel v7.0. We are also actively working on an upgrade script, for those of you on Drauger OS 7.7 to upgrade to 7.8 without needing a fresh re-install. We will announce when this is available.
ATTENTION ALL DRAUGER OS USERS The Drauger OS apt repo, download servers, and beta website are all going to be down intermittently over the next couple weeks as our ISP performs upgrades to our service. We apologize for the inconvenience!
Drauger OS 7.8, Beta 2, Code named Urgal, is now available! This release is mostly iterative: we removed a few unnecessary packages, restored linux-firmware (missed in Beta 1 😅), and rolled in updated software across the board. Keep an eye out for Beta 3 in a couple months! Bigger changes coming then!
ATTENTION Due to severe winter weather approaching the southeast, the Drauger OS apt repo, beta website, and download optimizer may go down due to power loss. We are aware of the risks and are working to minimize any possible issues. If you are in the area, please stay safe, and stay warm!
🎄 Drauger OS 7.8 Beta 1 “Urgal” is now available! As we wrap up the holiday season, we're pleased to present Drauger OS 7.8 Beta 1, codenamed Urgal. Please remember: this is an early beta, and bugs should be expected. For users who need a dependable gaming system or daily driver, Drauger OS 7.7 will remain supported until the stable 7.8 release arrives in roughly six months. 🎁 Key Changes - Rebased from Ubuntu 24…
Happy Holidays to you and yours! Big announcement coming Saturday! Stay tuned!
Preliminary look at Drauger OS 7.8, codename Urgal.
We're working on Drauger OS 7.8 right now, and we wanted to know how the community feels on an important topic. Should we ship Firefox ESR as a native package, or normal Firefox as a flatpak? So, thoughts? What would you prefer? Vote and discuss below!
- Native Package (Firefox ESR)31%
- Flatpak (Normal Firefox)69%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
I'm proud to announce that Drauger OS is now part of the Distrowatch database! Thanks to everyone for voting for us to get off the waitlist! https://distrowatch.com/table.php?distribution=drauger
Showing the 12 most recent of 20 posts we hold for @draugeros_news. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
We're working on Drauger OS 7.8 right now, and we wanted to know how the community feels on an important topic. Should we ship Firefox ESR as a native package, or normal Firefox as a flatpak? So, thoughts? What would you prefer? Vote and discuss below!
- Native Package (Firefox ESR)31%
- Flatpak (Normal Firefox)69%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 23 July 2024 to 4 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Drauger OS News” (@draugeros_news), 39 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/draugeros_news.
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.