фроксы оейейе☠☠
custom 51884583061836633734

Channel
@Cfsharplow
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,676subscribers
+515 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003995012812 |
|---|---|
| Type | Channel |
| Username | @Cfsharplow |
| Created | Between 1 April 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/Cfsharplow |
Adult — 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 54% 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 |
|---|---|---|
| 15 Sept 2026, 09:16 | 1,676 | +82 |
| 11 Sept 2026, 22:02 | 1,594 | +9 |
| 7 Sept 2026, 18:15 | 1,585 | +31 |
| 2 Sept 2026, 18:24 | 1,554 | +4 |
| 30 Aug 2026, 14:44 | 1,550 | +3 |
| 27 Aug 2026, 08:28 | 1,547 | +133 |
| 23 Aug 2026, 22:04 | 1,414 | +44 |
| 20 Aug 2026, 03:17 | 1,370 | +57 |
| 16 Aug 2026, 19:34 | 1,313 | +52 |
| 13 Aug 2026, 16:09 | 1,261 | +33 |
| 10 Aug 2026, 17:01 | 1,228 | +62 |
| 7 Aug 2026, 12:50 | 1,166 | +5 |
| 6 Aug 2026, 20:02 | 1,161 | no change |
| 6 Aug 2026, 19:51 | 1,161 | first reading |
19 posts held, back to 6 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 19 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
264 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 31.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5190754180951739632 | 82 | 31.1% | |
| custom 5188458306183663373 | 76 | 28.8% | |
| custom 5460716450580829149 | 50 | 18.9% | |
| custom 5391015071306520137 | 36 | 13.6% | |
| custom 5384507757766412445 | 20 | 7.58% |
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 14 of the 19 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 264 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 6 August 2026 to 6 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.
фроксы оейейе☠☠
custom 51884583061836633734
╰┈➤ִ ࣪ FROX!¡cf (NSFW) ˗ˏˋ ✉︎ ˎˊ˗ в этом кф можно увидеть или опубликовать контент по пейрингу фрогги&грокс, в котором нет жестких ограничений и цензуры . . . @FROXcf_NSFW ❝ будем ждать тебя!! ⤷ ゛⋮ TakeBot ! navigation ! Mp post ┆ ˎˊ˗ —
🤩 › #тейк ⋮ @Cfsharplow ‹ ✨ ›› cr wosiskw on 🎵
custom 51884583061836633731custom 51907541809517396321
ну этт месть за то что меня с сервера кикнули не удивляйтесь
что это тг
привет, не спрашивайте зачем но кому не лень тапните тут за @Dexterirlkisser ( копируется при нажатии ) посты будут да.. мне просто делать нехуй🥺 тапнуть можно только один раз с акка/канала ( у кого прем есть, гс актуально до 13:00 по мск ) грииин отпишись мнеее это месть грину
ᅠ❝︎ 🔤щете относительно новый флуд по всем майнфд ? в будущем планируется создать сервер для флуда … ✨ ▫️ᅠ❗🤩 инфо untitled флуда 🤩
Signed ۫𝓥 𝘪𝘯𝘴𝘦𝘯𝘵 ׄ ♡͟⋮ 𝅄 ׄ ㅤ︩︪໒𝙄𝒏𝒇𝒆𝒓𝒏𝒐 : ♡୧ ׄ ♡͟⋮ 𝅄 𝗋𖹭͜𝗌𝖾 ᠀᷼◌ #SL
@xvishiko тгк › #тейк ⋮ @Cfsharplow ‹
custom 51907541809517396329custom 51884583061836633736custom 53910150713065201373custom 53845077577664124452custom 54607164505808291492
Signed шарплоу тейки
Шарплоу как куколки их ещё и переодевать можно Тгк: @jessdoitnow › #тейк ⋮ @Cfsharplow ‹
custom 546071645058082914918custom 51884583061836633739custom 53845077577664124457custom 51907541809517396323custom 53910150713065201372
Signed шарплоу тейки
можете скинуть несколько пнг с шарплоу.... у меня не получается норм вырезать , оч над о для эдита мне😢😢 › #тейк ⋮ @Cfsharplow ‹
custom 51884583061836633735custom 51907541809517396321custom 53845077577664124451
Signed шарплоу тейки
шарп готовил Арт канал: @qwxxkp_pucyet › #тейк ⋮ @Cfsharplow ‹
custom 539101507130652013712custom 51884583061836633736custom 51907541809517396325custom 53845077577664124452custom 54607164505808291491
Signed шарплоу тейки
- «я сказал «да»» - «было сложно, но я сглазил», но тут шарпнесс, джуд и тай тгк: @realqnooo (не подписывайтесь) › #тейк ⋮ @Cfsharplow ‹
custom 519075418095173963219custom 518845830618366337312custom 54607164505808291494custom 53910150713065201373
Signed шарплоу тейки
Showing the 12 most recent of 19 posts we hold for @Cfsharplow. 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.
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 14 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.
@Cfsharplow 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“𝖲𝖧𝖠𝖱𝖯𝖫𝖮𝖶 𝖢𝖥” (@Cfsharplow), 1,676 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/Cfsharplow.
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.