FEG Community Update Regarding BitMart Exchange BitMart has announced that it is beginning an orderly wind-down of its exchange operations. The FEG funds currently held on BitMart have been paused from withdrawal. Because those funds cannot currently be accessed, we will stop FEG trading on BitMart to protect users and prevent additional orders from accumulating. The funds currently affected are limited to approxi…

Channel
FEG (Feed Every Gorilla)
@fegtoken
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
9,770subscribers
-31 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001364057050 |
|---|---|
| Type | Channel |
| Username | @fegtoken |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/fegtoken |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 13:05 | 9,770 | -8 |
| 10 Aug 2026, 18:28 | 9,778 | -15 |
| 7 Aug 2026, 19:43 | 9,793 | -8 |
| 6 Aug 2026, 21:15 | 9,801 | no change |
| 6 Aug 2026, 21:07 | 9,801 | first reading |
Engagement
20 posts held, back to 6 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.34%
- avg views ÷ 9,770 subscribers
- Avg views / post
- 619
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 26 July 2026 |
|---|---|
| Posts held | 20 (6 August 2025 – 26 July 2026) |
| Views total | 619 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 05:52 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Video runtime
- 4m 40s
- Average length
- 56s
Measured directly from 5 videos 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.
Recent posts
Today we celebrate the Dads, father figures, builders, protectors, and everyday heroes in our community. Feed Every Gorilla. Strong. Smart. Legendary. Happy Father’s Day, FEG Family! 💪🦍❤️ https://x.com/i/status/2068821572534862327
📈 Bonding Curve Update: Thank you for your patience, and a special thank you to our public testers and team members who have continued providing valuable feedback throughout testing. Through both internal team review and public tester suggestions, that feedback has helped drive several important changes and additions. While this has extended the mainnet release timeline, these updates are being made to strengthen t…
🦍 The FEG team had an excellent meeting this weekend, and development continues moving quickly behind the scenes. Public Bonding Curve testing has already delivered valuable feedback, strong engagement, and several community requested improvements now being integrated. ✅ Explore page coming within the next 24-48 hours ✅ UI upgrades for Bonding Curve token pages based directly on community feedback ✅ Improved visual…
🚨 The next evolution of SmartDeFi™ is LIVE for public testing! FEG’s new Bonding Curve presale model with integrated referrals is ready for the community to test. 💬 Join the SD Bonding Curve Test Topic Chat to participate and share feedback: https://t.me/FEGchat/6874170 🔗 Test here: https://testnet.smartdefi.com 🦊 For the best experience, we recommend using MetaMask. What’s live: 📈 Dynamic Bonding Curve price d…
We are pushing this again as part of our CEX efforts. MEXC is requiring that our community hold at least $50,000 USD worth of FEG to be held on their exchange at all times to remain compliant for listing. We were meeting that requirement until the recent market drop in both FEG and BNB brought the value below their threshold. To stay aligned and avoid any issues, we need the community’s support over the next 48 ho…
🎉 Happy 5th Birthday $FEG Half a Decade of Relentless DeFi Innovation Five years ago, FEG was born from frustration with rug pulls and broken promises, and a belief that DeFi could be safer, stronger, and built to last. What began as a community-driven movement grew into real infrastructure with one goal, raising the standard for DeFi. The journey was not easy. As a young project breaking new ground, we faced str…
FEG Team Meeting Recap January 10th, 2026 The meeting focused on alignment across technology, execution, and forward momentum, with a clear message that the project is firmly in a build and expansion phase. It was reiterated that progress is being driven by infrastructure and core systems rather than surface-level updates, and that this approach is intentional. A major portion of the discussion centered around the …
As we close the year and reflect, 2025 was not about noise, it was about foundations. FEG has been building since January 2021, through every phase of the market, while hype driven projects came and went. In 2025: ✅️ SmartDeFi™ Launchpad infrastructure shipped and matured ✅️ Bonding Curve Presales were built, audited by Hacken, implemented, and entered final testing ✅️ SmartDeFi.com was hardened across frontend, b…
🎄 Merry Christmas Eve FEG Family! If you’re traveling tonight, take it easy, get there safe & sound! The charts can wait, your people can’t 🙏 Much love to everyone in the community, enjoy the night, the food, & the time together 🍌✨ 💪🦍❤️🎄
SmartDeFi.com Development Update Frontend framework upgrade (Angular 21) The frontend was upgraded to Angular 21. Core components were refactored to work with the latest APIs, and performance and build optimizations were applied. This improves site speed, stability, and long-term maintainability. Wallet and contract interaction upgrade (Wagmi v3) The Wagmi library was migrated to v3. Contract interaction logic was …
FEG's 6 month chart out of 5 years of life! 🦍 FEG.io 0xf3c7cecf8cbc3066f9a87b310cebe198d00479ac We've already put in our move, digested it, and spent months shaking out weak hands without collapsing. No panic, no capitulation, just controlled downside and seller exhaustion. Now you’re seeing compression and a clean bounce off the lows. That’s how bases get built before momentum comes back! Quiet charts like this …
Showing the 12 most recent of 20 posts we hold for @fegtoken. 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
Citation-graph rank — 179,722 of 1,345,403entries 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.
Forward network
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.
Mentions
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“FEG (Feed Every Gorilla)” (@fegtoken), 9,770 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/fegtoken.
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.