Telegram RegisterThe public register of Telegram
Telegram profile photo for ꣑୧ㅤчеթ𝖾꯭шня феოцеꪒ 🍒

Channel

꣑୧ㅤчеթ𝖾꯭шня феოцеꪒ 🍒

@femcheriecos

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

103subscribers

+20 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003906965222
TypeChannel
Username@femcheriecos
CreatedBetween 1 April 2026 and 6 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live24 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 24 September 2026
On Telegramt.me/femcheriecos

Growth

83103939 August 2026 — 83 subscribers9 August 2026 — 83 subscribers17 August 2026 — 88 subscribers1 September 2026 — 89 subscribers10 September 2026 — 97 subscribers24 September 2026 — 103 subscribers9 August 202624 September 2026
6 measurements spanning 46 days, net +20. 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 80–106 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Sept 2026, 23:21103+6
10 Sept 2026, 18:5997+8
1 Sept 2026, 15:1689+1
17 Aug 2026, 10:3888+5
9 Aug 2026, 18:0083no change
9 Aug 2026, 12:1783first reading

Engagement

18 posts held, back to 6 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 9 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

354 reactions across 15 posts, in 25 distinct kinds. The most used accounts for 18.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54249516394317392916718.9%
custom 54249668779757035444312.1%
custom 5424862213917668421349.60%
custom 5454325324496000774246.78%
custom 5354931152677281903226.21%
custom 5256002825896366661195.37%
custom 5255825868948803809174.80%
custom 5255848396052271199174.80%
custom 5339337419210657530143.95%
custom 5193049888216076813133.67%
custom 5377666209871322444133.67%
custom 5377663216279117758123.39%
custom 525593217368434755492.54%
custom 530332614565823974592.54%
custom 538889654862297671792.54%
custom 521969875153850328071.98%
custom 531426306512913312351.41%
custom 537741775889815259951.41%
custom 529857772001011601841.13%
custom 529864821760331340141.13%
5 further kinds71.98%

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 15 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 354 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 6 July 2026 to 9 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.

Recent posts

9 Aug 2026, 14:02 UTC41 views22 reactionsread 9 August 2026
Photo

РЕБЯТ ПРТВЕТ???

custom 542495163943173929110custom 54249668779757035447custom 54248622139176684215

9 Aug 2026, 10:48 UTC51 views32 reactionsread 9 August 2026
Photo

уже на месте, НО выступать буду в третьем блоке 🎀🎀

custom 545432532449600077414custom 54248622139176684217custom 54249516394317392917custom 53888965486229767174

8 Aug 2026, 09:06 UTC61 views11 reactionsread 9 August 2026

Posted without readable text

custom 54249668779757035447custom 51930498882160768132custom 54248622139176684212

3 Aug 2026, 14:00 UTC140 views23 reactionsread 9 August 2026
Photo

скоро...🌸

custom 519304988821607681310custom 54249668779757035446custom 54543253244960007746custom 53976304290438948991

30 Jul 2026, 14:10 UTC189 views19 reactionsread 9 August 2026
Photo

. . . на сколько тейков в подслушке тянет ? 🤩🤩

custom 54249516394317392919custom 54248622139176684215custom 54543253244960007744custom 54249668779757035441

26 Jul 2026, 19:27 UTC217 views19 reactionsread 9 August 2026
Photo

сжарилась на солнце ✅️ натерла ноги ✅️ сломала украшение ✅️ 〰️〰️ как всегда плохо брат 🎶 из контента только эта тупая фотка блин. очень жду фотки с фото зоны, но постараюсь отфоткать контента сама, а ещё выйти в нем скоро на меро, НО ЭТОГО Я ВАМ НЕ ГОВОРИЛА УПС— 🌟 спасибо дориану, карасику и дейдиззик за этот день. последних двух поздравляю с первым местом кстати 🌟🌟

custom 54249516394317392919custom 54249668779757035445custom 54248622139176684213custom 53888965486229767172

26 Jul 2026, 09:04 UTC185 views17 reactionsread 9 August 2026
Photo

а я уже еду 🌟

custom 542495163943173929110custom 54249668779757035444custom 54248622139176684213

25 Jul 2026, 17:20 UTC194 views15 reactionsread 9 August 2026

🤯🥹Омега Шин, уставший от навязчивого ухаживания альфы Соу, случайно вкалывает себе загадочный препарат — и превращается в доминантного монстра. Теперь он сам решает, как наказать Соу за все прошлые приставания. Жестоко, властно, без компромиссов. А когда эффект проходит, Соу уже слишком напуган, чтобы ослушаться. Читать далее...

custom 54249516394317392917custom 54248622139176684214custom 54249668779757035444

23 Jul 2026, 08:30 UTC296 views23 reactionsread 9 August 2026
Photo

🌟🌟🌟🤩🤩🤩🤩🤩 🤩🥹 〰️🥹2️⃣6️⃣🅰️0️⃣7️⃣буду присутствовать на а-дзин фесте в хаджиме шино 🤩 вместе со своей девочкой-неформалочкой в харуке сакурае 🌟🥹🥹🥹 🥹🥹🥹буду рада со всеми увидеться, пофоткаться и ответить на вопрос на чем же у меня держится хвост 🌟🌟🌟 🥹🤩🥹

custom 54249668779757035448custom 54248622139176684215custom 54249516394317392915custom 53888965486229767173custom 51930498882160768131custom 52695950702432953721

21 Jul 2026, 17:29 UTCviews —

Channel name was changed to «꣑୧ㅤчеթ𝖾꯭шня феოцеꪒ 🍒»

Showing the 12 most recent of 18 posts we hold for @femcheriecos. 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.

Forward network

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.

Mentions

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

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.

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 24 September 2026 — this entry's latest reading, not the date you are reading this.

“꣑୧ㅤчеթ𝖾꯭шня феოцеꪒ 🍒” (@femcheriecos), 103 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/femcheriecos.

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.