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

Channel

Curvance Announcements

@curvance

On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

1,901subscribers

-20 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001714975892
TypeChannel
Username@curvance
Created26 November 2021measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live4 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/curvance

Growth

1,9011,9211,9117 August 2026 — 1,921 subscribers7 August 2026 — 1,921 subscribers7 August 2026 — 1,920 subscribers11 August 2026 — 1,915 subscribers13 August 2026 — 1,912 subscribers16 August 2026 — 1,909 subscribers19 August 2026 — 1,908 subscribers23 August 2026 — 1,905 subscribers26 August 2026 — 1,904 subscribers4 September 2026 — 1,901 subscribers7 August 20264 September 2026
10 measurements spanning 28 days, net -20. 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 1,898–1,924 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 18:001,901-3
26 Aug 2026, 02:041,904-1
23 Aug 2026, 03:231,905-3
19 Aug 2026, 17:231,908-1
16 Aug 2026, 22:041,909-3
13 Aug 2026, 17:361,912-3
11 Aug 2026, 00:231,915-5
7 Aug 2026, 19:301,920-1
7 Aug 2026, 10:311,921no change
7 Aug 2026, 10:231,921first reading

Engagement

5 posts held, back to 26 November 2021the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 pages 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 5 posts for this entry, the most recent from 22 February 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 May 2023, 23:23 UTC≈2,000 viewsread 7 August 2026

If you haven't already joined our public chat you can join here: https://t.me/CurvanceChat

5 Jan 2022, 19:24 UTC≈3,330 viewsread 7 August 2026

I seem to forget to update the telegram announcements channel, the majority of the community is based on Discord and I suggest joining if you are not there yet! discord.gg/curvance

26 Nov 2021, 20:37 UTC≈3,350 viewsread 7 August 2026

Welcome to the Curvance Announcements channel We are building the largest lending protocol for the Curve ecosystem starting with Curve, Convex and Yearn wraps For investment/business inquiries please contact @mikecurvance ‼️PLEASE BE AWARE WE DO NOT HAVE A TOKEN YET, ANY LISTINGS OF $CVE AT THIS TIME ARE UNOFFICIAL‼️ We look forward to delivering updates as our development progresses! Official Links: www.curvanc

Showing the 5 most recent of 5 posts we hold for @curvance. 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

Named by 3 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Hemi -- News & Updates
@hemi_news · 34,378
Telegram ranks this channel #25 of 83 here — alongside 82 others — read 3 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Curvance Announcements” (@curvance), 1,901 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/curvance.

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.