Telegram RegisterThe public register of Telegram
Telegram profile photo for ๐—ฐ๐—ฎ๐—ฟ๐˜รฉ๐˜€๐—ถ๐—ฒ๐—ป ๐—ผ๐—ณ๐—ณ๐—ถ๐—ฐ๐—ถ๐—ฎ๐—น๐˜€

Channel

๐—ฐ๐—ฎ๐—ฟ๐˜รฉ๐˜€๐—ถ๐—ฒ๐—ป ๐—ผ๐—ณ๐—ณ๐—ถ๐—ฐ๐—ถ๐—ฎ๐—น๐˜€

@cartesiennes

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

100subscribers

+8 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002964054382
TypeChannel
Username@cartesiennes
Created22 October 2025 โ€” measured โ€” dated from the channelโ€™s first post
First recorded9 August 2026
Last confirmed live30 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/cartesiennes

Growth

92100968 August 2026 โ€” 92 subscribers9 August 2026 โ€” 92 subscribers15 August 2026 โ€” 97 subscribers30 August 2026 โ€” 100 subscribers8 August 202630 August 2026
4 measurements spanning 22 days, net +8. 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 91โ€“101 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 10:55100+3
15 Aug 2026, 19:0897+5
9 Aug 2026, 13:4792no change
8 Aug 2026, 11:3392first reading

Engagement

9 posts held, back to 22 October 2025 โ€” 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 pageof 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 9 posts for this entry, the most recent from 22 October 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

22 Oct 2025, 17:07 UTCโ‰ˆ2,650 viewsread 9 August 2026

ใ…คใ…ค ๐“’artesien officials pls dm only one admin at a time to prevent order confusion & double dropping. any form of disrespect will not be entertained. be respectful! โ€Ž โ€Ž โ€Ž owner โฆ‚ @Iustres co-owner โฆ‚ @Iumiuno admins โฆ‚ admin luxie : @Iustresaide user id : 7839744150 ๐Ÿฆ‹ admin luciv : @Iustrestant user id : 8269479418 ๐Ÿฆ‹ admin lusci :โ€ฆ

22 Oct 2025, 16:30 UTCโ‰ˆ2,130 viewsread 9 August 2026

ใ…คใ…ค ๐—น๐—ฒ๐—ด๐—ถ๐˜ ๐—ฐ๐—ต๐—ฒ๐—ฐ๐—ธ๐˜€ ใ…ค for @Iustres 01. 02. 03. 04. 05. 06. 07. 08. 09. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. ใ…ค for @Iustresadmin 01. 02. 03. 04. 05. 06. 07. 08. 09. 10. 11. ใ…ค for @Iustresaide 01. 02. 03. 04. ใ…ค for @Iustrestant 01. 02. 03. 04. 05. 06. 07. 08. 09. 10. 11. 12. 13. 14.โ€ฆ

22 Oct 2025, 16:13 UTCโ‰ˆ1,300 viewsread 9 August 2026
Photo

ใ…คใ…ค visit @cartesienshop to navigate other channel links

22 Oct 2025, 16:03 UTC980 viewsread 9 August 2026

๐Ÿธ lfb netflix, disney, spotify, canva bulk, yt, ms365, picsart, gamecreds @aboutcartesien @cartesieninv

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

Citation-graph rank

Citation-graph rank โ€” 1,015,397 of 1,628,524entries in the measured graph. A weighted position computed from the forward and mention edges below โ€” republished posts weigh more than named mentions โ€” and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channelโ€™s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page โ€” a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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

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 30 August 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œ๐—ฐ๐—ฎ๐—ฟ๐˜รฉ๐˜€๐—ถ๐—ฒ๐—ป ๐—ผ๐—ณ๐—ณ๐—ถ๐—ฐ๐—ถ๐—ฎ๐—น๐˜€โ€ (@cartesiennes), 100 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/cartesiennes.

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.