Froge$FROGE
Risk analysis for Froge (FROGE) on Robinhood — contract 0x1249a3544fbdb3a81763550d3191dc3724f1d3ec. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Scanned 2026-09-30 15:25 UTC
Multiple health signals are weakening, and a launch-pattern cluster acquired 53.7% of supply, but independent wallet linkage is not fully corroborated.
Technical snapshot
Trading indicators and observed activity
Technical snapshot
Market structure, order flow and published on-chain evidence from one chain-specific snapshot.
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.
Market overview
Market overview
Market data
Trading activity
Markets & liquidity pools
Markets & liquidity pools
Primary indexed pool
0x06B6990d80867434d43C0E0d38C896162f356911The page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is Froge?
What is Froge?
Froge ($FROGE) is a ERC-20 token on the Robinhood blockchain Its primary trading venue is uniswap, with roughly $79.91K in live on-chain liquidity. It currently has 2,334 on-chain holders, and was first traded 1 month old. Rug.Tools' current assessment of Froge is "Elevated Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
Rug.Tools signals
Rug.Tools signals
Key statistics
Key statistics
Launch activity
Stored funding, acquisition and wallet evidenceRug.Tools analysis
Rug.Tools analysis

Multiple health signals are weakening, and a launch-pattern cluster acquired 53.7% of supply, but independent wallet linkage is not fully corroborated.
Verdict from canonical snapshot b3086c40 · v3 · scanned 2026-09-30 15:25 UTC · page content updated 2026-09-30 15:25 UTC
Holder distribution
Holder distribution
Creator profile
Creator profile
0x837b17e34a931979aad3c052feaf1b73098b9953Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
Token activity
- 2026-09-15 17:03 UTCToken launchedFirst on-chain trading pair opened on uniswap.
- 2026-09-30 15:25 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 Froge?⌄
Froge is a Robinhood token analyzed by Rug.Tools using public on-chain data — holders, liquidity, creator wallet activity and contract security signals. This page shows the latest cached analysis and refreshes automatically.
Is Froge safe?⌄
Current Rug.Tools verdict: Elevated Risk. Multiple health signals are weakening, and a launch-pattern cluster acquired 53.7% of supply, but independent wallet linkage is not fully corroborated. No token can be guaranteed safe: verdicts summarize on-chain risk signals only and cannot detect off-chain intent. Always do your own research.
How many holders does Froge have?⌄
Rug.Tools currently sees 2,334 holders. The largest holder account holds 1.55% of supply; the top 10 holder accounts together hold 5.73%. These balances alone do not establish individual ownership or independent control.
Where is Froge traded?⌄
The primary trading venue detected on Robinhood is uniswap. Review the market and liquidity evidence below; trading venue availability does not establish token safety.
How often does this page update?⌄
This page renders from cached data in our database. It refreshes when a new scan runs — either on a scheduled background sync or when a user clicks Refresh above. Opening this page does not trigger a new scan.