Telegram RegisterThe public register of Telegram
Telegram profile photo for ag𔘓ny.

Channel

ag𔘓ny.

@curoryne

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

140subscribers

-12 since we began measuring on 14 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002159143998
TypeChannel
Username@curoryne
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live7 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/curoryne

Growth

14015214614 August 2026 — 152 subscribers14 August 2026 — 152 subscribers15 August 2026 — 151 subscribers22 August 2026 — 145 subscribers30 August 2026 — 146 subscribers7 September 2026 — 140 subscribers14 August 20267 September 2026
6 measurements spanning 24 days, net -12. 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 138–154 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 15:36140-6
30 Aug 2026, 04:46146+1
22 Aug 2026, 21:45145-6
15 Aug 2026, 09:44151-1
14 Aug 2026, 14:00152no change
14 Aug 2026, 13:47152first reading

Engagement

20 posts held, back to 24 June 2026the 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 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

87 reactions across 7 posts, in 9 distinct kinds. The most used accounts for 14.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53707979515746300621314.9%
custom 53953514077275082001314.9%
custom 52603733158972873261213.8%
custom 53685681205186650911112.6%
custom 5267461656908164014910.3%
custom 5979009958283318728910.3%
custom 5981260332167860928910.3%
custom 539582723426931690766.90%
custom 539541154156460672555.75%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 8 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 87 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 24 June 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
16
across the posts below
Posts paid on
8
of 20 we hold a reading for · 40%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @curoryne. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 24 June 2026 to 3 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

3 Aug 2026, 23:06 UTC135 views0 reactions3 Starsread 14 August 2026

Black lipstick stains her glass of red wine, I am your servant, may I light your cigarette?

3 Aug 2026, 22:55 UTC115 views14 reactions2 Starsread 14 August 2026
File

File, posted without a caption

custom 53707979515746300627custom 53953514077275082007

3 Aug 2026, 22:41 UTC101 views12 reactions2 Starsread 14 August 2026
File

File, posted without a caption

custom 53707979515746300626custom 53953514077275082006

24 Jul 2026, 22:11 UTC183 views9 reactions3 Starsread 14 August 2026
Photo

Photo, posted without a caption

custom 52674616569081640149

24 Jul 2026, 22:10 UTC173 viewsread 14 August 2026

"𝑎𝑛𝑑 𝑠𝑢𝑑𝑑𝑒𝑛𝑙𝑦, 𝑡𝒉𝑒 𝑙𝑎𝑘𝑒, 𝑖𝑡𝑠 𝑤𝑎𝑡𝑒𝑟𝑠 𝒉𝑎𝑟𝑑 𝑎𝑛𝑑 𝒉𝑖𝑑𝑑𝑒𝑛, 𝑐𝑜𝑚𝑝𝑎𝑐𝑡𝑒𝑑 𝑙𝑖𝑔𝒉𝑡, 𝑗𝑒𝑤𝑒𝑙 𝑠𝑒𝑡 𝑖𝑛 𝑎 𝑟𝑖𝑛𝑔 𝑜𝑓 𝑒𝑎𝑟𝑡𝒉. 𝐴 𝑏𝑙𝑎𝑐𝑘—𝑎𝑛𝑑—𝑤𝒉𝑖𝑡𝑒 𝑓𝑙𝑦𝑖𝑛𝑔: 𝑡𝒉𝑒 𝑠𝑤𝑎𝑛𝑠 𝑡𝑜𝑜𝑘 𝑓𝑙𝑖𝑔𝒉𝑡, 𝑙𝑜𝑛𝑔 𝑛𝑒𝑐𝑘𝑠 𝑜𝑓 𝑛𝑖𝑔𝒉𝑡, 𝑓𝑒𝑒𝑡 𝑜𝑓 𝑟𝑒𝑑 𝑙𝑒𝑎𝑡𝒉𝑒𝑟, 𝑎𝑛𝑑 𝑎 𝑝𝑙𝑎𝑐𝑖𝑑 𝑠𝑛𝑜𝑤 𝑓𝑙𝑦𝑖𝑛𝑔 𝑜𝑣𝑒𝑟 𝑡𝒉𝑒 𝑤𝑜𝑟𝑙𝑑.

24 Jul 2026, 22:10 UTC166 viewsread 14 August 2026

𝑂𝒉, 𝑡𝒉𝑒 𝑓𝑙𝑖𝑔𝒉𝑡 𝑓𝑟𝑜𝑚 𝑡𝒉𝑒 𝑚𝑖𝑟𝑟𝑜𝑟𝑖𝑛𝑔 𝑤𝑎𝑡𝑒𝑟, 𝑎 𝑡𝒉𝑜𝑢𝑠𝑎𝑛𝑑 𝑏𝑜𝑑𝑖𝑒𝑠 𝑎𝑖𝑚𝑒𝑑 𝑎𝑡 𝑎 𝑏𝑒𝑎𝑢𝑡𝑖𝑓𝑢𝑙 𝑠𝑡𝑖𝑙𝑙𝑛𝑒𝑠𝑠 𝑙𝑖𝑘𝑒 𝑡𝒉𝑒 𝑡𝑟𝑎𝑛𝑠𝑝𝑎𝑟𝑒𝑛𝑡 𝑝𝑒𝑟𝑚𝑎𝑛𝑒𝑛𝑐𝑒 𝑜𝑓 𝑡𝒉𝑒 𝑙𝑎𝑘𝑒.

24 Jul 2026, 22:10 UTC170 viewsread 14 August 2026

𝑆𝑢𝑑𝑑𝑒𝑛𝑙𝑦, 𝑎𝑙𝑙 𝑤𝑎𝑠 𝑟𝑎𝑐𝑖𝑛𝑔 𝑜𝑣𝑒𝑟 𝑡𝒉𝑒 𝑤𝑎𝑡𝑒𝑟, 𝑚𝑜𝑣𝑒𝑚𝑒𝑛𝑡, 𝑠𝑜𝑢𝑛𝑑, 𝑡𝑜𝑤𝑒𝑟𝑠 𝑜𝑓 𝑡𝒉𝑒 𝑓𝑢𝑙𝑙 𝑚𝑜𝑜𝑛, 𝑎𝑛𝑑 𝑡𝒉𝑒𝑛, 𝑤𝑖𝑙𝑑 𝑤𝑖𝑛𝑔𝑠, 𝑤𝒉𝑖𝑐𝒉 𝑜𝑢𝑡 𝑜𝑓 𝑡𝒉𝑒 𝑤𝒉𝑖𝑟𝑙𝑤𝑖𝑛𝑑 𝑡𝑢𝑟𝑛𝑒𝑑 𝑖𝑛𝑡𝑜 𝑜𝑟𝑑𝑒𝑟, 𝑓𝑙𝑖𝑔𝒉𝑡, 𝑟𝑒𝑎𝑙𝑖𝑧𝑒𝑑 𝑣𝑎𝑠𝑡𝑛𝑒𝑠𝑠, 𝑎𝑎𝑛𝑑 𝑡𝒉𝑒𝑛 𝑎𝑏𝑠𝑒𝑛𝑐𝑒, 𝑎 𝑤𝒉𝑖𝑡𝑒 𝑠𝒉𝑖𝑣𝑒𝑟𝑖𝑛𝑔 𝑖𝑛 𝑡𝒉𝑒 𝑣𝑜𝑖𝑑."

9 Jul 2026, 21:16 UTC269 views18 reactions1 Starread 14 August 2026
Photo

Photo, posted without a caption

custom 59790099582833187289custom 59812603321678609289

6 Jul 2026, 22:06 UTC242 viewsread 14 August 2026

شب مرگ، از بیم ، آنجا شتابد که از مرگ غافل شود تا بمیرد، من این نکته گیرم ، که باور ندیدم که قویی به صحرا بمیرد، چو روزی ز آغوش دریا شبی هم در آغوش دریا بمیرد، تو دریای من بودی، آغوش وا کن،که می خواهد این قوی زیبا بمیرد.

6 Jul 2026, 22:02 UTC233 viewsread 14 August 2026

شب مرگ ،تنها، نشیند به موجی رود گوشه ای دور و تنها بمیرد، در آن گوشه چندان غزل خواند آن شب، که خود در میان غزل ها بمیرد، گروهی برآنند کاین مرغ شیدا کجا عاشقی کرد، آنجا بمیرد.

6 Jul 2026, 22:01 UTC243 viewsread 14 August 2026

شنیدم که چون قوی زیبا بمیرد، فریبنده زاد و فریبا بمیرد

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“ag𔘓ny.” (@curoryne), 140 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/curoryne.

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.