Telegram RegisterThe public register of Telegram
Telegram profile photo for Chorus

Channel

Chorus

@chorusmc

On this record: Topic · Growth · Engagement · Posts · Cite this entry

80subscribers

+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-1001390595720
TypeChannel
Username@chorusmc
CreatedBetween 1 March 2018 and 23 January 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live7 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/chorusmc

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

7981807 August 2026 — 79 subscribers9 August 2026 — 79 subscribers27 August 2026 — 81 subscribers7 October 2026 — 80 subscribers7 August 20267 October 2026
4 measurements spanning 61 days, net +1. 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 79–81 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 19:1880-1
27 Aug 2026, 21:4781+2
9 Aug 2026, 19:3179no change
7 Aug 2026, 20:3579first reading

Engagement

20 posts held, back to 23 January 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 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 16 September 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

16 Sept 2023, 17:26 UTC353 viewsread 9 August 2026
Photo

Chorus 1.4 is finally OUT! 🎉 Download it from chorus.iamgio.eu - don’t use the auto-updater for this version. 📄 Changelog (with also a small note from @iAmGio)

23 Aug 2023, 17:25 UTC277 viewsread 9 August 2026

As for the next major update, the development has been idle for a while due to studies and other projects. I hope to release 1.4 - possibly Chorus' last major release - before the new year. Also, Chorus is now 5 years old! 🎂

23 Aug 2023, 17:20 UTC259 viewsread 9 August 2026

chorusmc.org now redirects to chorus.iamgio.eu, and will keep doing so until the domain's expiration in mid-2024. After that, chorus.iamgio.eu will be the only way to access Chorus' website.

8 Sept 2022, 21:55 UTC331 viewsread 9 August 2026

Chorus can now be built with Maven in a snap. While the new version is still under development, it is now easier to compile the cloned source code via the mvn clean install command to built a cross-platform executable and access the newest features. https://github.com/iamgio/chorus

7 Jun 2022, 18:16 UTC369 viewsread 9 August 2026

On its 4th birthday, Chorus has reached 5k all-time downloads! 🎂 I’m so grateful you still enjoy using Chorus and I hope to get back working on it as soon as possible 🙏

13 Nov 2021, 14:30 UTC477 viewsread 9 August 2026

I also want to take this opportunity to update you about the status of Chorus. The development has been stale for two months since I (@iAmGio) have moved to another city to study at university. Now that I have settled in I have more time to work on my projects, including Chorus. New features will arrive soon! 🤞

14 Jun 2021, 22:07 UTC398 viewsread 9 August 2026

Also, particles, effects and sounds are now updated to all versions from 1.12 to 1.16. 1.17 will be added soon.

14 Jun 2021, 22:05 UTC373 viewsread 9 August 2026

A huge change in terms of performance has been implemented: reflection calls have been minimized and game components (items, entities, etc) are now dynamically loaded when needed. This results in more speed and less memory usage. Commit: 955443a

10 Jun 2021, 11:14 UTC343 viewsread 9 August 2026

Chorus 1.3.2 is out with a couple hotfixes, including Chinese not being properly loaded.

7 Jun 2021, 15:00 UTC405 viewsread 9 August 2026

Chorus 1.3.1 is OUT! 🥳 Download it from chorusmc.org (built-in updaters from 1.3 and below won't work because of the newly-added standalone MacOS executable). Happy editing! 📄 Changelog

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

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

“Chorus” (@chorusmc), 80 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/chorusmc.

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.