Channel
@CLTFM
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
29subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001952951816 |
|---|---|
| Type | Channel |
| Username | @CLTFM |
| Created | 2 October 2023 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/CLTFM |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 21:25 | 29 | no change |
| 11 Aug 2026, 14:47 | 29 | first reading |
12 posts held, back to 2 October 2023 — 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 12 posts for this entry, the most recent from 9 November 2025. An engagement rate over an empty window would be a number about nothing.
94 reactions across 9 posts, in 15 distinct kinds. The most used accounts for 21.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5222400230133081714 | 20 | 21.3% | |
| custom 5334665104677941170 | 11 | 11.7% | |
| custom 5289862389552919154 | 10 | 10.6% | |
| custom 5219901967916084166 | 9 | 9.57% | |
| custom 5244820603663296299 | 8 | 8.51% | |
| custom 5222148368955877900 | 7 | 7.45% | |
| custom 5219672809936006424 | 5 | 5.32% | |
| custom 5260424249914435335 | 5 | 5.32% | |
| custom 5335005820138564214 | 5 | 5.32% | |
| custom 5258196742435787040 | 4 | 4.26% | |
| custom 5377377257356537351 | 4 | 4.26% | |
| ❤🔥 | 3 | 3.19% | |
| custom 5219943216781995020 | 1 | 1.06% | |
| custom 5222472119295684375 | 1 | 1.06% | |
| custom 5334811859415477124 | 1 | 1.06% |
Custom emoji. 14 of the rows above are 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 areTelegram’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 10 of the 12 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 94reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 2 October 2023 to 9 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 27 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
новый юз рубиджейн - @sexyjanka.
custom 52224002301330817141custom 53348118594154771241
Signed párker.
милые мои знм, это рубиджейн. я приношу свои извинения за то, что приключилось, но аккаунт рубиджейн не удалось вернуть. мы не нашли никакую информацию о номере, хотя искали очень долго, всю ночь. поэтому, у меня уже нет сил и стараний возвращать все сначало. эра знаменитых окончательна подошла к концу. прощайте любимые. удачи вам в продвижении. я вас любила. ( @rubyjenka ) #celebritesinfo •• важное.
custom 52224002301330817145custom 52199432167819950201
Signed clt كاليستا
разрыв
custom 52224002301330817146
Signed ронничка شكرا clt
здравствуйте. на связи админ знаменитых, сулу. у влд, рубиджейн ( @rubyjenka ), слетел акк. она очищала телефон, и кэш на нем, и потеряла доступ к этому аккаунту. номер был покупной, и наизусть она его не знает. сейчас доступа к этому каналу у неё нет, и прав у админов сделать её с другого акка администратором канала тоже нет. возможно у кого-то из вас был подобный случай, и вы знаете как восстановить аккаунт, будем…
custom 52224002301330817141custom 52224721192956843751custom 52898623895529191541
Signed párker. معجب clt
Sticker, posted without a caption
custom 52224002301330817142
Signed rùbyjánę’ ไทก้า ‚ clt xzá
люблю руби причина: она моя кисуня.
custom 52224002301330817141
Signed rùbyjánę’ ไทก้า ‚ clt xzá
Sticker, posted without a caption
Signed rùbyjánę’ ไทก้า ‚ clt xzá
ㅤ ㅤ post active 🦋 хэллоу, знмэшки. скучали по посту на актив? вот и он. доброе утро, уже кушали? 1. давайте просто познакомимся. как вас зовут? 2. что вы любите делать, а что нет? 3. работаете , учитесь? 4. что вам доставляет счастье? 5. го др? ❤️🔥 #celebritespostactive
custom 52224002301330817144custom 52898623895529191542custom 53346651046779411702
Signed rùbyjánę’ ไทก้า ‚ clt xzá
Sticker, posted without a caption
❤🔥3
ㅤㅤ💜 #NÁVÌGÁTÍÒN .. fr clt ** union - ` ¡! RULES - chat ” . . @ ◄ツ 💜 patent & info ¿ ° hastags . .
custom 52199019679160841669custom 53346651046779411709custom 52448206036632962998custom 52221483689558779007custom 52898623895529191547custom 52196728099360064245custom 52604242499144353355custom 53350058201385642145
Channel created
Showing the 12 most recent of 12 posts we hold for @CLTFM. 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 — 392,973 of 1,160,990entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@CLTFM named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“@néw èrá . . #𝘾𝙀𝙇𝙀𝘽𝙍𝙄𝙏𝙀𝙎 ??” (@CLTFM), 29 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/CLTFM.
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.