
Flying Avocado Cat$FAC
Risk analysis for Flying Avocado Cat (FAC) on Ethereum — contract 0x1a3a8cf347b2bf5890d3d6a1b981c4f4432c8661. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Recorded explanation unavailable. Review the report evidence and verification limits.
Reliability & unknowns
Low confidence describes evidence coverage, quality and freshness, not token safety. Verification status unavailable.
• The report evidence is stale or its observation time is invalid; confidence is limited.
LP protection: check the full canonical report for independently verified lock, burn or withdrawal evidence. Indexed wiki flags alone do not prove protection.
Technical snapshot
Trading indicators and observed activity
Technical snapshot
Market data and stored security analysis are separate observations; check their timestamps before comparing numbers.
Available depth relative to valuation
24h volume divided by liquidity
Transaction split unavailable
Across 1h, 6h and 24h returns
How to read these technicals
Turnover measures trading activity against available liquidity. High turnover can also mean volatility.
Momentum alignment compares overlapping return windows. It is context, not independent confirmation or a safety score.
Holder concentration uses the published report’s classified holder evidence when available.
Freshness is the age of Rug.Tools’ indexed market snapshot, separate from the report scan time.
Price chart
Price chart
Price chart
Load verified candle history to explore price and volume directly in this report.
What is Flying Avocado Cat?
What is Flying Avocado Cat?
Flying Avocado Cat ($FAC) is a ERC-20 token on the Ethereum blockchain. Its displayed indexed holder snapshot reports 3,312 holder accounts. Rug.Tools has not verified a current risk assessment of Flying Avocado Cat; the displayed status is "Analysis Pending".
Rug.Tools signals
Rug.Tools signals
Key statistics
Key statistics
Launch activity
Native receipt, wallet and liquidity custody evidenceRug.Tools analysis
Rug.Tools analysis

Last analyzed 2026-07-23 08:16 UTC
Holder distribution
Holder distribution
Indexed holder figures; their original observation time is unverified. They are separate from the canonical verdict and may describe a different snapshot.
Only recorded top-ten shares are shown; remaining supply, infrastructure custody, and control are not inferred.
Creator profile
Creator profile
0x523d890747b827b5bf48b1a0b483e690ed23f932Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
Token activity
- 2026-07-23 08:16 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
Similar tokens
Compared using stored market cap, launch age and trading venue. Similarity is not a safety rating.
Finding comparable tokens…
Learn more
Frequently asked questions
Frequently asked questions
What is Flying Avocado Cat?⌄
Flying Avocado Cat is a Ethereum token analyzed by Rug.Tools using available public on-chain data. Holder observations, indexed market data, and the stored risk verdict may have different observation times.
Is Flying Avocado Cat safe?⌄
Stored Rug.Tools verdict: Analysis Pending (canonical report unavailable). The verdict is based on available on-chain signals only. A stored verdict does not prove current safety or future intent. Always do your own research.
How many holders does Flying Avocado Cat have?⌄
The displayed indexed holder data reports 3,312 holders, largest measured holder 3.22% and top ten 12.23%. Original holder observation time is unverified. These figures are historical measurements, not proof of independent control.
Where is Flying Avocado Cat traded?⌄
Rug.Tools has not yet detected an active trading pair for this token on Ethereum. Liquidity may be very low or the pool may have moved.
How often does this page update?⌄
This page shows cached reports and indexed market observations. Values change when new evidence is recorded or published; opening the page does not trigger a scan.