мне искренне жаль эту начинающую мейкершу, потому что она начала снимать в тт. (в лк я ее не видел) в тик токе явно не за человечность ㅤ 彡take. . –>> @catmaker_cfbot
💘2

Channel
@catmaker_cf
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
89subscribers
+9 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003767242714 |
|---|---|
| Type | Channel |
| Username | @catmaker_cf |
| Created | Between 1 February 2026 and 29 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/catmaker_cf |
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 06:55 | 89 | +5 |
| 10 Sept 2026, 00:38 | 84 | -2 |
| 1 Sept 2026, 04:15 | 86 | +4 |
| 18 Aug 2026, 10:08 | 82 | +3 |
| 11 Aug 2026, 22:23 | 79 | -1 |
| 11 Aug 2026, 21:45 | 80 | no change |
| 11 Aug 2026, 21:32 | 80 | first reading |
18 posts held, back to 29 July 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 18 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
34 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 32.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😡 | 11 | 32.4% | |
| ❤🔥 | 8 | 23.5% | |
| 💘 | 5 | 14.7% | |
| 🤡 | 4 | 11.8% | |
| 👎 | 3 | 8.82% | |
| 👍 | 2 | 5.88% | |
| 🥱 | 1 | 2.94% |
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 12 of the 18 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 34 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 29 July 2026 to 11 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.
мне искренне жаль эту начинающую мейкершу, потому что она начала снимать в тт. (в лк я ее не видел) в тик токе явно не за человечность ㅤ 彡take. . –>> @catmaker_cfbot
💘2
Коты воители. Чо за хуйня ㅤ 彡take. . –>> @catmaker_cfbot
❤🔥2
соц опрос что сейчас с багряным? скажите пожалуйста кто знает, раньше следила за ним, очень крутой и как человек, и как мейкер. Хочется узнать что случилось и что с ней сейчас. ㅤ 彡take. . –>> @catmaker_cfbot
На ком по вашему мнению держится весь фд? ㅤ 彡take. . –>> @catmaker_cfbot
тригг на пестри начнем с ее "оригинальности". девочка рисует своей оске кровь из носа, который все юзали в 2021-22 году и называет это своей идеей 😐..во вторых она провела мега нечестный конкурс, аргументировав это тем, что это ее конкурс, и она будет решать какие арты будут на призовых. я бы воспринял это без негатива, но она блять расставила туда арты с фонами из пинтерест и без рендера сука🥀 еще и принизила арт м…
🤡4👎3💘3❤🔥2👍2🥱1
😿 — #вп
❤🔥1
🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 А меня бесит .. , У неё нет анатомии😬 — Знакомо❎ · 🅰️elcome ↓↓ 🐾 "Cat-artist" trigger Выскажи любое 🅰️🅰️🅰️🅰️🅰️🅰️🅰️🅰️🅰️🅰️ мнение насчет художников которые рисуют котов здесь анонимно!! 🦋 Навигация | администрация 🕸 Бот → @CatArtistTriggerbot
Когда был ваш Прайм?? ㅤ 彡take. . –>> @catmaker_cfbot
Как я вижу фд КетМейкера сейчас: ㅤ 彡take. . –>> @catmaker_cfbot
😡2
как вы думаете , прощаем кеку? (она извинилась перед всеми мейкерами в своем канале) ㅤ 彡take. . –>> @catmaker_cfbot
😡3
вы видели кеку извинилась ㅤ 彡take. . –>> @catmaker_cfbot
😡2
Кеку возвращается в фд кет мейкера.. (нам всем пиздец) ㅤ 彡take. . –>> @catmaker_cfbot
😡2
Showing the 12 most recent of 18 posts we hold for @catmaker_cf. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
@catmaker_cf 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“彡𝘩𝘢𝘵𝘦.𝘭𝘰𝘷𝘦 𝘤𝘢𝘵𝘮𝘢𝘬𝘦𝘳— 𝘤𝘰𝘯𝘧𝘦𝘴𝘴𝘪𝘰𝘯!” (@catmaker_cf), 89 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/catmaker_cf.
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.