Telegram RegisterThe public register of Telegram
Telegram profile photo for Canary Announcements

Channel

Canary Announcements

@CanaryAnnouncements

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

33subscribers

-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-1001525565556
TypeChannel
Username@CanaryAnnouncements
CreatedBetween 1 August 2021 and 10 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live27 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 27 August 2026
On Telegramt.me/CanaryAnnouncements

Growth

3234337 August 2026 — 34 subscribers11 August 2026 — 34 subscribers14 August 2026 — 32 subscribers21 August 2026 — 33 subscribers7 August 202621 August 2026
4 measurements spanning 14 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 32–34 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 05:1533+1
14 Aug 2026, 13:1532-2
11 Aug 2026, 00:1634no change
7 Aug 2026, 11:3934first reading

Engagement

20 posts held, back to 10 August 2021the 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 19 February 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

19 Feb 2024, 14:57 UTC302 viewsread 11 August 2026

Auto-Burn Alert! 📢 Yet another 568,888 $CNR tokens go up in flames! 🔥 Our innovative Auto-burn feature keeps the fire burning every 5 days, paving the way for a brighter future! 🔄

Signed Canary Developers🔺Never DM first!

7 Dec 2023, 11:56 UTC84 viewsread 11 August 2026

Auto-Burn Alert! 🔥✨ 568,888 CNR has just been burned! 🔥 Thanks to the revolutionary Auto-burn feature, this blazing journey continues every 5 days! 🔄

Signed Canary Developers🔺Never DM first!

19 Oct 2023, 19:35 UTC225 viewsread 11 August 2026
Photo

Photo, posted without a caption

Signed Canary Developers🔺Never DM first!

16 Apr 2022, 21:07 UTC353 viewsread 11 August 2026
Photo

https://twitter.com/CanaryDefi/status/1515436633620946951

Signed Canary Developers🔺Never DM first!

16 Feb 2022, 22:34 UTC402 viewsread 11 August 2026

https://twitter.com/CanaryDex/status/1494077562728988687

Signed Canary Developers🔺Never DM first!

3 Feb 2022, 08:10 UTC351 viewsread 11 August 2026

https://twitter.com/CanaryDex/status/1489149078697095169

Signed Canary Developers🔺Never DM first!

30 Jan 2022, 13:56 UTC320 viewsread 11 August 2026

— 📢 Announcement 📢 It's almost time for New Canary launch. If nothing goes wrong, we want to open it until Thursday, February 3, at the latest. The reason for this small delay is that we want to launch both the CNR-AVAX super farm on Pangolin and the double reward CNR-AVAX farm on NewCanary at the same time. Get ready for a great new "Canary" experience and powerful CNR 👊

Signed Canary Developers🔺Never DM first!

11 Nov 2021, 20:37 UTC545 viewsread 11 August 2026

https://twitter.com/CanaryDex/status/1458896457319301127

Signed Canary Developers | Never DM first !

4 Nov 2021, 11:10 UTC466 viewsread 11 August 2026

https://twitter.com/CanaryDex/status/1456213186441515008

Signed Canary Developers | Never DM first !

27 Oct 2021, 20:16 UTC643 viewsread 11 August 2026

https://twitter.com/BoogeyBirds/status/1453454490103951367

Signed Canary Developers | Never DM first !

11 Oct 2021, 20:20 UTC602 viewsread 11 August 2026

https://twitter.com/CanaryDex/status/1447658022231236623

Signed Canary Developers | Never DM first !

7 Oct 2021, 10:24 UTC407 viewsread 11 August 2026

https://twitter.com/CanaryDex/status/1446026728871182339

Signed Canary Developers | Never DM first !

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

Mentions

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.

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

“Canary Announcements” (@CanaryAnnouncements), 33 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/CanaryAnnouncements.

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.