Hacker House$HACKHOUSE
Risk analysis for Hacker House (HACKHOUSE) on Solana — contract 9zRNZjZZC94Rgw1ddwzfvqkdJDQpmn9rhmGiqPyVpump. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
sampled holder accounts hold 21.8% of supply.
Reliability & unknowns
Low confidence describes evidence coverage, quality and freshness, not token safety. Verification status unavailable.
• The observed pool is under 24 hours old; the existing confidence policy limits this report to Low. Pool age is not itself a risk finding.
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.
Solana snapshot
More details⌄
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
BjC5egtrLovHyLWAhiNnMdv41GKVyKh3NqhDpGrfJ2kLThe page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is Hacker House?
What is Hacker House?
Hacker House ($HACKHOUSE) is a SPL token on the Solana blockchain Its primary trading venue is pumpfun. It currently has 194 on-chain holders, and was first traded new (today). Rug.Tools' current assessment of Hacker House is "Analysis Pending", 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 evidenceRug.Tools analysis
Rug.Tools analysis

sampled holder accounts hold 21.8% of supply.
Last analyzed 2026-10-30 15:30 UTC
Holder distribution
Holder distribution
Creator profile
Creator profile
DjM7Tu7whh6P3pGVBfDzwXAx2zaw51GJWrJE3PwtuN7sToken activity
Token activity
- 2026-10-30 15:25 UTCToken launchedFirst on-chain trading pair opened on pumpfun.
- 2026-10-30 15:30 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 Hacker House?⌄
Hacker House is a Solana 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 Hacker House safe?⌄
Current Rug.Tools verdict: Analysis Pending. sampled holder accounts hold 21.8% of supply. 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 Hacker House have?⌄
Rug.Tools currently sees 194 holders. The largest holder account holds 3.57% of supply; the top 10 holder accounts together hold 21.82%. These balances alone do not establish individual ownership or independent control.
Where is Hacker House traded?⌄
The primary trading venue detected on Solana is pumpfun. 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.