𝗳𝗿𝗲𝘀𝗵𝗹𝘆 𝗰𝘂𝗿𝗮𝘁𝗲𝗱 𝗽𝗶𝗲𝗰𝗲𝘀 +𝟸𝟸 ❀ now await their rightful gardien; 5.000 — 🐩 *:·. :: tender your forms and lay claim with limpidité and candeur.

Channel
. . </ acellyiez ᐠ..ৎ୭
@acellyiez
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,685subscribers
-38 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001663657082 |
|---|---|
| Type | Channel |
| Username | @acellyiez |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/acellyiez |
Topic
Other / unclassifiable — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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, 17:22 | 1,685 | -33 |
| 17 Sept 2026, 05:58 | 1,718 | -10 |
| 12 Sept 2026, 19:41 | 1,728 | -25 |
| 8 Sept 2026, 16:57 | 1,753 | -19 |
| 7 Sept 2026, 19:22 | 1,772 | no change |
| 3 Sept 2026, 02:17 | 1,772 | -15 |
| 31 Aug 2026, 10:06 | 1,787 | -23 |
| 28 Aug 2026, 00:34 | 1,810 | -10 |
| 24 Aug 2026, 23:17 | 1,820 | -9 |
| 21 Aug 2026, 06:52 | 1,829 | -10 |
| 18 Aug 2026, 14:33 | 1,839 | -7 |
| 15 Aug 2026, 06:25 | 1,846 | -19 |
| 12 Aug 2026, 08:26 | 1,865 | +104 |
| 9 Aug 2026, 05:51 | 1,761 | +38 |
| 8 Aug 2026, 18:53 | 1,723 | first reading |
Engagement
15 posts held, back to 9 August 2026 — 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 15 posts for this entry, the most recent from 13 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Sticker, posted without a caption
𝗺𝗼𝗿𝗻𝗶𝗻𝗴 𝗮𝗿𝗿𝗶𝘃𝗲𝗱 𝗮𝗹𝗺𝗼𝘀𝘁 𝘂𝗻𝗻𝗼𝘁𝗶𝗰𝗲𝗱 🍽🪽pale light rested upon linen curtains, a cup of tea cooling beside the window ✿ִ𝆬 the day remained ( à 𝘥𝘦𝘮𝘪-é𝘷𝘦𝘪𝘭𝘭é &, ) ౨ৎ. t.me/acellyiez 𝙾𝙿𝙴𝙽𝚂. ⠾ 𝚁𝙴𝙶𝚄𝙻𝙰𝚃𝙸𝙾𝙽𝚂 ︴ 𝚁𝙴𝙰𝙳𝚈 ︴ 𝙿𝚁𝙸𝙲𝙴𝙻𝙸𝚂𝚃 ︴ 𝙲𝙰𝚁𝙴𝚃𝙰𝙺𝙴𝚁𝚂 not yet asking to be carried. everything felt familiar in a way that could scarcely be ୭ৎ ˖ 𝘯𝘢𝘮𝘦𝘥, 𝘢 𝘧𝘦𝘦𝘭𝘪𝘯𝘨 𝘵𝘰𝘶𝘫𝘰𝘶𝘳𝘴
Sticker, posted without a caption
𝘁𝗵𝗲 𝗲𝘃𝗲𝗻𝗶𝗻𝗴 𝘀𝗼𝗹𝗶𝗰𝗶𝘁𝘀 𝗻𝗼 𝗰𝗹𝗮𝗺𝗼𝘂𝗿 ✉️ ° ₊☾ ︴ a diminutive candle smoulders upon the bedside table, its fragrance ( 𝘱𝘳𝘦𝘴𝘲𝘶𝘦 𝘰𝘶𝘣𝘭𝘪é𝘦 &, ) as though recalled from another season. ›❀;t.me/acellyiez 𝙲𝙻𝙾𝚂𝙴𝚂. a journal lies parted to an unmarked leaf, words arriving with retenue— not profusely, merely in measures sufficient to relinquish the 🍽*:·. ( 𝟸𝟸.𝟶𝟶, 𝘥𝘢𝘺'𝘴 𝘲𝘶𝘪𝘦𝘵 𝘢𝘤𝘤𝘶𝘮𝘶𝘭𝘢𝘵𝘪𝘰𝘯𝘴
Sticker, posted without a caption
𝗳𝗿𝗲𝘀𝗵𝗹𝘆 𝗰𝘂𝗿𝗮𝘁𝗲𝗱 𝗽𝗶𝗲𝗰𝗲𝘀 +𝟸𝟸 ❀ now await their rightful gardien; 6.000 — 🐩 *:·. :: tender your forms and lay claim with limpidité and candeur.
Sticker, posted without a caption
𝗳𝗿𝗲𝘀𝗵𝗹𝘆 𝗰𝘂𝗿𝗮𝘁𝗲𝗱 𝗽𝗶𝗲𝗰𝗲𝘀 +𝟸𝟸 ❀ now await their rightful gardien; 5.000 — 🐩 *:·. :: tender your forms and lay claim with limpidité and candeur.
Sticker, posted without a caption
𝗳𝗿𝗲𝘀𝗵𝗹𝘆 𝗰𝘂𝗿𝗮𝘁𝗲𝗱 𝗽𝗶𝗲𝗰𝗲𝘀 +𝟸𝟸 ❀ now await their rightful gardien; 6.000 — 🐩 *:·. :: tender your forms and lay claim with limpidité and candeur.
Sticker, posted without a caption
Showing the 12 most recent of 15 posts we hold for @acellyiez. 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 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“. . </ acellyiez ᐠ..ৎ୭” (@acellyiez), 1,685 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/acellyiez.
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.