Channel
@fanexacrm
On this record: Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
120subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002183275477 |
|---|---|
| Type | Channel |
| Username | @fanexacrm |
| Created | 18 October 2024 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/fanexacrm |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 21:37 | 120 | -2 |
| 9 Aug 2026, 03:30 | 122 | no change |
| 7 Aug 2026, 15:22 | 122 | first reading |
15 posts held, back to 18 October 2024 — 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 15 posts for this entry, the most recent from 10 September 2025. An engagement rate over an empty window would be a number about nothing.
50 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 62.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 31 | 62.0% | |
| 🔥 | 7 | 14.0% | |
| 😢 | 4 | 8.00% | |
| 👍 | 3 | 6.00% | |
| 🤡 | 2 | 4.00% | |
| 🌚 | 1 | 2.00% | |
| 👀 | 1 | 2.00% | |
| 🥱 | 1 | 2.00% |
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 9 of the 15 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 50 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 18 October 2024 to 10 September 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.
🚀 Fanexa is for sale: code, website, community, and admin dashboard Our team is shifting focus to other projects. Rather than slow the pace, we want Fanexa to grow under a dedicated owner who can scale it. Included: * Full codebase for Windows and Mac, plus a nearly ready web app with Dashboard, Chats, Vault, and Automations * Admin dashboard for user management, roles and permissions, billing, usage monitoring, a…
😢4🤡2
FANEXA – FANSLY CRM [05.07.2025] 🚀 Web App Release Imminent! Hey everyone, We’re thrilled to announce that the brand-new Fanexa Web App is launching soon—full-featured, browser-based access from anywhere! ✨ New Web App Features - Instant Browser Access: Jump into your Dashboard, Chats, and Vault—no downloads required. - Seamless Updates: Always on the latest version, automatically. - Full Feature Suite: Scripts, …
👍2❤1👀1
📣 Introducing the Fansly Management Network! 💼🤝 We're excited to launch something new and powerful for all Fansly managers and creators who want to grow smarter — together. ✨ Fansly Management Network 🔹 Connect with other Fansly managers and share your insights 🔹 Discuss growth strategies, client handling, and creator success 🔹 Stay updated on Fansly platform changes and trends 🔹 Collaborate and level up your manag…
FANEXA - FANSLY CRM [26.04.2025] 🚀 New Features and Fixes This Week! Hey everyone, We’re excited to announce HUGE new features and important improvements to Fanexa! ✨ New Feature: Scripts Scripts are here to supercharge your workflow! - Configure Scripts with videos, pictures, messages, and a custom price. - Easily send them to your customers in just a few clicks. - Overview what has already been sent to each cust…
❤2
🚀 Fanexa is Back Online – Now Cheaper, Faster, and Smoother Than Ever! 🌐 We’re thrilled to announce that Fanexa is officially back up and better than ever! Thanks to your patience and support, we’ve completed essential upgrades to deliver top performance, enhanced reliability, and an even smoother experience. ✨ What’s New: ⚡️ Improved Performance: Enjoy faster load times, quicker analytics, and seamless navigation…
❤5👍1
🚀 Big Update Incoming: Major Improvements After Maintenance! 🛠 We’ve been hard at work behind the scenes to make Fanexa faster, more reliable, and better than ever. As part of these upgrades, we've implemented crucial backend improvements and introduced a new pricing model that better supports creators of all sizes. Recently, we encountered scaling challenges and realized that our backend needed a major upgrade to …
❤2
🚀 Fanexa Beta Release – Manage Your Fansly Agency Smarter! We’re launching our beta version, bringing you the ultimate all-in-one tool to manage and grow your Fansly accounts effortlessly. ✨ Key Features: - 🔒 Secure Account Sharing: Share access with team members without revealing passwords. Set roles and control permissions effortlessly. - 📊 Advanced Analytics: Track and boost account performance with in-depth in…
Photo, posted without a caption
FANEXA - FANSLY CRM, [09.02.2025] 🚀 New Fixes and Improvements This Week! Hey everyone, We’ve been hard at work improving Fanexa, and here’s what’s been fixed and updated this week: 🛠️ Avatar picture upload now works seamlessly. 🛠️ Unlimited loading wheel issue in the enhanced chat has been resolved. 🛠️ Removing and adding a creator is now smoother than ever. 🛠️ Our pricing system has been revamped to make it simp…
❤5
FANEXA - FANSLY CRM pinned a photo
🚀 Fanexa Update: Version Progress and New Features in Development! 🔧✨ We’ve got some exciting news! 🎉 Since our last update, we’ve moved from version 1.0.9 to 1.0.13, fixing numerous bugs to make the platform more stable and user-friendly. ✅ Thanks to your amazing feedback, we’re now working on these exciting new features: Auto-messages that are sent when a fan comes online. 💬 The ability to add customers to lists…
❤2
FANEXA IS IN THE TESTING PHASE! 🎉 Hey everyone, After a long wait, we’re finally ready to start testing! 🚀 Our CEO, Tim, gave us a quick overview of the software, and now we’d love to have some of you try it out. If you’re interested, please message @timsiwild with the following details: Whether you use Mac or Windows The number of models you manage We’re planning to release Fanexa in the next 1-2 weeks, and your …
🔥5❤4
Showing the 12 most recent of 15 posts we hold for @fanexacrm. 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.
@fanexacrm 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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“FANEXA - FANSLY CRM” (@fanexacrm), 120 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/fanexacrm.
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.