RUG.TOOLS
Headroom$HOOM
Risk analysis for Headroom (HOOM) on Robinhood — contract 0x59b666ba51d4d313a7e56ba058e0bd236b627777. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Scanned 2026-10-30 03:25 UTC
- 1.CRITICAL RED FLAG · Project Lifecycle
Liquidity or market activity has collapsed. Lifecycle evidence alone does not confirm deliberate liquidity removal.
Why it matters: Weakening activity or liquidity can impair exits; deterioration alone is not proof of deliberate fraud.
- 2.Unclassified Contract Concentration
An unclassified contract holds 97.81% of supply. Its purpose and control remain unverified.
Why it matters: Review the underlying recorded evidence; this does not establish malicious intent.
- 3.Largest Holder Account
One holder account holds 97.8% of supply; independent control is not established.
Why it matters: Review the underlying recorded evidence; this does not establish malicious intent.
See 5 additional recorded findings
- 4. Sampled Holder Accounts
sampled holder accounts hold 100.0% — high concentration.
Why it matters: Review the underlying recorded evidence; this does not establish malicious intent.
- 5. Liquidity
Very thin liquidity ($4,584) — a trading risk (heavy slippage), not proof of a scam.
Why it matters: Limited available liquidity can make large trades expensive or difficult to exit; a market quote is not proof of LP protection.
- 6. Coordinated Wallet Activity
Reported historical launch exposure: 87.3% of supply. Evidence confidence: medium. Creator allocations and transfers may be included; purchases, common ownership and insider attribution are not established. A Critical module finding describes potential severity, while the overall verdict requires corroborated evidence. Complete launch coverage and wallet-specific transaction links could change the classification.
Why it matters: Historical launch exposure can create concentration risk. It does not establish current balances, common wallet control, or executed bundles.
- 7. Historical launch exposure
A sampled launch-window group of 175 tracked wallets reached up to 87.28% of supply.
Why it matters: Historical exposure does not prove common wallet control, and it cannot be added to current holdings.
- 8. Reported liquidity depth
$4,583.5 in tracked liquidity in the recorded market snapshot.
Why it matters: Trading depth affects slippage and exit difficulty. Market-reported liquidity does not establish a verified LP lock or current executable quote.
Reliability & unknowns
Low confidence describes evidence coverage, quality and freshness, not token safety. checks incomplete.
• Required verification checks are incomplete; category availability does not establish completed verification.
• The report evidence is stale or its observation time is invalid; confidence is limited.
• 0/175 launch-wallet balances measured; 175 remain unknown. Present group holdings are not fully measured.
LP protection: not verified. Wallet attribution and independent control require separate evidence.
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 provider unavailable — showing last verified values from 14 hours ago.
Market data
Trading activity
Markets & liquidity pools
Markets & liquidity pools
Primary indexed pool
0x3c80AEacEB7705B08e333d95aF26EBD1C93F9A59The page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is Headroom?
What is Headroom?
Headroom ($HOOM) is a ERC-20 token on the Robinhood blockchain Its primary trading venue is uniswap, with roughly $4.58K in live on-chain liquidity. It currently has 10 on-chain holders, and was first traded new (today). Rug.Tools' current assessment of Headroom is "Market Collapse", 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
Native receipt, wallet and liquidity custody evidenceNative evidence explorer
Launch, wallet flows & liquidity custody
Inspect what was observed, which balances were measured, and what remains unverified. Timing and transfers alone do not establish common ownership or a sale.
Investigate creator trades & token transfers
Forensic intelligence / Activity
What did the developer actually do?
Separate current holdings, historical launch exposure, verified sales and token transfers. Follow the receipts before drawing conclusions.
- Creator holdings
- 0.00%
- Historical launch exposure
- 87.28%
Saved balance measurement; separate from sale history
Observed launch-group share of total token supply; not every graph node, developer sales or present insider ownership
Developer sales: Insufficient Evidence · Trading integrity: Not Scored. A creator holding 0% does not establish whether tokens were sold or transferred.
Launch evidence
222 observed recipients
518 receipts examined
Current cohort balances
Unknown
0/175 wallets measured · 175 unknown
Custody coverage
1 custody accounts / markets
1 without verified protection
Token custody and LP withdrawal protection are separate checks.
Creator provenance
0x5397…c964 · 0.00% current measured holdings
Attribution: rpc-creation-trace. Identified wallet only; this does not establish total team ownership.
Deployment receipt: 0xcebe…e3a8
Launch timeline & receipt references
Anchor block #101,186,259 · observed through #101,191,258 · Reconstruction captured:
| From anchor | Recipients | Net inflow / supply | Evidence |
|---|---|---|---|
| +0 blocks | 1 | 98.89% | Verified interval |
| +2 blocks | 1 | 98.89% | Verified interval |
| +5 blocks | 1 | 98.89% | Verified interval |
| +10 blocks | 1 | 98.89% | Verified interval |
Intervals include the anchor through the stated offset. Net inflows are token movements recorded in those receipts, divided by supply measured at replay time; they are not confirmed purchases or current holdings. Partial replay may omit inflows or outflows. Historical values are not clamped into ownership claims.
- 0xcebe…e3a8 · #101,186,259
- 0x0310…d0c8 · #101,186,778
- 0x1074…db1f · #101,186,778
- 0x2f7f…ee06 · #101,186,778
- 0x3a3a…5817 · #101,186,778
- 0x4f72…dfec · #101,186,778
- 0x5327…c7a7 · #101,186,778
- 0x6616…8f7c · #101,186,778
- 0x6665…fce8 · #101,186,778
- 0x687d…a74f · #101,186,778
- 0x6dc0…76db · #101,186,778
- 0x876c…5f51 · #101,186,778
- 0x9d8b…e1e8 · #101,186,778
- 0xa1b7…78e4 · #101,186,778
- 0xa1e1…e014 · #101,186,778
- 0xa4be…eb8a · #101,186,778
Pool-by-pool custody & protection
97.81% of token supply in custody · reported role / market
An infrastructure classification does not establish ownership or withdrawal protection for an individual liquidity position.
Measured wallet balances & transfer evidence
A measured zero balance does not prove a sale. Unknown balances are not zero. Only 40 stored sample rows are listed; aggregate coverage includes missing rows.
| Recipient | Current balance | First position | Receipt references |
|---|---|---|---|
| 0xcaff…4487 | Unknown | #101,186,778 | 0x9d8b…e1e8 |
| 0x7e3c…c0c8 | Unknown | #101,186,781 | Not stored |
| 0x6d79…27a5 | Unknown | #101,186,778 | 0xf256…7159 |
| 0x8823…4f75 | Unknown | #101,186,778 | 0x6dc0…76db |
| 0xc7d8…6d76 | Unknown | #101,186,778 | 0xfc4e…12d9 |
| 0x4058…6408 | Unknown | #101,186,778 | 0x3a3a…5817 |
| 0x481a…5b6f | Unknown | #101,186,778 | 0xad7b…5780 |
| 0x443c…c66e | Unknown | #101,186,781 | Not stored |
| 0x648b…683f | Unknown | #101,186,778 | 0x876c…5f51 |
| 0x2240…c2e0 | Unknown | #101,186,778 | 0xd390…58b30xb1c4…1bc8 |
| 0x2dd2…c0e9 | Unknown | #101,186,781 | Not stored |
| 0x7d21…160b | Unknown | #101,186,778 | 0xa1b7…78e4 |
| 0x771a…1b25 | Unknown | #101,186,778 | 0x6616…8f7c |
| 0x1318…927c | Unknown | #101,186,780 | 0x19e9…ab88 |
| 0xecf1…af97 | Unknown | #101,186,778 | 0x6665…fce8 |
| 0x7439…6834 | Unknown | #101,186,778 | 0x687d…a74f0x5991…040d |
| 0xbebb…f27b | Unknown | #101,186,780 | Not stored |
| 0x53d3…b4ba | Unknown | #101,186,781 | Not stored |
| 0x5cec…af8a | Unknown | #101,186,780 | Not stored |
| 0xff8c…f8eb | Unknown | #101,186,780 | Not stored |
| 0xb3c8…7594 | Unknown | #101,186,778 | 0x1074…db1f |
| 0xa800…5d3e | Unknown | #101,186,780 | Not stored |
| 0xf792…c4ed | Unknown | #101,186,781 | Not stored |
| 0x0f2d…1a69 | Unknown | #101,186,780 | 0xf706…459e |
| 0x8f95…92b3 | Unknown | #101,186,778 | 0x2f7f…ee06 |
| 0xdae4…d12b | Unknown | #101,186,781 | Not stored |
| 0x824c…c3d6 | Unknown | #101,186,778 | 0xba70…2a90 |
| 0x60a3…3726 | Unknown | #101,186,780 | Not stored |
| 0xc763…98f1 | Unknown | #101,186,780 | Not stored |
| 0xf22a…956d | Unknown | #101,186,781 | Not stored |
| 0xf5db…5d7d | Unknown | #101,186,781 | Not stored |
| 0xb448…d000 | Unknown | #101,186,780 | Not stored |
| 0x83f5…7f6f | Unknown | #101,186,778 | 0x0310…d0c8 |
| 0x5789…8fc3 | Unknown | #101,186,778 | 0xa1e1…e014 |
| 0xf596…60b4 | Unknown | #101,186,780 | Not stored |
| 0xcdfc…6dfe | Unknown | #101,186,780 | Not stored |
| 0x1a2e…34de | Unknown | #101,186,780 | 0x4efa…c35d |
| 0x93d2…8215 | Unknown | #101,186,778 | 0x5327…c7a7 |
| 0x1c9d…42dd | Unknown | #101,186,780 | 0xf009…6e5a |
| 0x0322…45f1 | Unknown | #101,186,780 | 0x15b5…d0a9 |
Source snapshot: . This evidence explorer does not independently change the Rug.Tools verdict. Existing risk findings, verification gates and source timestamps remain authoritative.
RugGraph / Wallet intelligenceLinked-wallet graph25 wallets · 18 transaction references. Follow the receipts from saved launch evidence.Open wallet graph ↓
01 / Launch activity
Select a wallet to see its activity near token launch. Early receipt of tokens alone does not prove a sniper purchase.
Cyan: tokens received · Amber: tokens moved out · Dashed: deployment. Lines connect wallets to the launch sample; they do not identify who sent the tokens. The first 12 wallets are plotted; every listed wallet can be inspected below.
0x53979c89125a997189f80a8ff51c142ca543c964
Creator attribution
Balance at last observation
Unknown
Time unavailable · observation, not a live balance
02 / Funding connections
Where did the funding come from?
Follow verified transfers back up to three wallets. Select any connected wallet to explore its evidence.
Enhanced funding history is unavailable on this chain or snapshot. The saved report remains available above.
Evidence first. Ownership stays unproven.
A transfer proves funds moved between addresses. It does not prove they belong to the same person. Known exchange, bridge and pool accounts are marked as infrastructure.
How to read this evidence
Arrows show receipt references associated with the launch sample. They do not identify transfer counterparties or establish common ownership.
An early recipient is not necessarily a buyer or sniper. Outflows may be transfers; these summaries do not establish realized sales.
Balance measurements retain their original timestamps. Historical launch exposure is separate from present holdings.
Funding paths, verified swap activity and volume manipulation require additional transaction evidence. Missing history is unknown.
Source snapshot: 2026-10-30 03:25:26 UTC · Funding research runs only when requested.
Rug.Tools analysis
Rug.Tools analysis
Liquidity or market activity has collapsed. This lifecycle signal alone does not confirm a liquidity drain. Limited Robinhood Coverage — on-chain contract checks could not be checked and was not counted for or against this token.
Verdict from canonical snapshot bc666a90 · v3 · scanned 2026-10-30 03:25 UTC · page content updated 2026-10-30 03:25 UTC
Holder distribution
Holder distribution
Creator profile
Creator profile
0x53979c89125a997189f80a8ff51c142ca543c964Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
Token activity
- 2026-10-29 20:39 UTCToken launchedFirst on-chain trading pair opened on uniswap.
- 2026-10-30 03: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 Headroom?⌄
Headroom 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 Headroom safe?⌄
Current Rug.Tools verdict: Market Collapse. Liquidity or market activity has collapsed. This lifecycle signal alone does not confirm a liquidity drain. Limited Robinhood Coverage — on-chain contract checks could not be checked and was not counted for or against this token. 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 Headroom have?⌄
Rug.Tools currently sees 10 holders. The largest holder account holds 97.81% of supply; the top 10 holder accounts together hold 100.00%. These balances alone do not establish individual ownership or independent control.
Where is Headroom 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.