RUG.TOOLSPumpOnboard$PUMPONB
Risk analysis for PumpOnboard (PUMPONB) on Solana — contract Gr3cKLxXjrAnKfcxgQXip5dciCM5Bi3GXfGaD7cPpump. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Total tracked liquidity
$367.49
Combined across tracked pools. Individual pools can have much less liquidity; the total is not an executable exit quote.
Market snapshot · Observation time unavailable · Snapshot values are not live quotes.
Per-pool amounts were not recorded in this snapshot. The total must not be read as the primary pool's liquidity.
Scanned 2026-10-18 00:45 UTC
- 1.Holder concentration
Multiple health signals are weakening, and one holder account holds 14.3% of supply, and sampled holder accounts hold 39.0% of supply, and liquidity is very thin, so trades will move the price sharply.
Why it matters: Limited available liquidity can make large trades expensive or difficult to exit; a market quote is not proof of LP protection.
- 2.Reported liquidity depth
$367.49 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.
- 3.Top 10 individual wallet concentration
The reported top 10 individual wallets hold 38.97% of supply, using the report's holder classification and coverage.
Why it matters: Concentration can increase potential sell pressure. Wallet addresses do not establish distinct beneficial owners or independent control.
See 1 additional recorded findings
- 4. Creator wallet holdings
The identified creator wallet has 2.31% of supply in the recorded balance observation.
Why it matters: This measures the identified wallet only; it does not prove related-wallet holdings, creator intent, or future sales.
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.
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
6NgkRouTz4JZwqzBRre9jgQ1j2bma5BdAohYPNXTCo7fThe page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is PumpOnboard?
What is PumpOnboard?
PumpOnboard ($PUMPONB) is a SPL token on the Solana blockchain Its primary trading venue is meteora, with roughly $367 in live on-chain liquidity. It currently has 166 on-chain holders, and was first traded 12 days old. Rug.Tools' current assessment of PumpOnboard 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
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
- 2.31%
- Historical launch exposure
- Unknown
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
0 stored cohort rows
Interval evidence only; full launch coverage is reported separately.
Receipt-level replay was not stored for this snapshot.
Current cohort balances
Unknown
Recipient cohort not recorded
Observation time unavailable
Custody coverage
1 custody accounts / markets
1 without verified protection
Token custody and LP withdrawal protection are separate checks.
Creator provenance
HTG4jC…ag6Z · 2.31% current measured holdings
Attribution: mint_transaction. Identified wallet only; this does not establish total team ownership.
Launch timeline & receipt references
This older snapshot contains a recipient cohort, not the full receipt timeline. Counts and timing describe only the stored sample. Exact interval supply figures and transaction references remain unknown until a bounded native replay records them.
Pool-by-pool custody & protection
23.11% of token supply in custody · reported role / market · vault 2oVJgQ…jWW8
Token custody does not verify LP position ownership, locks or withdrawal protection.
Measured wallet balances & transfer evidence
A measured zero balance does not prove a sale. Unknown balances are not zero. Only 0 stored sample rows are listed; aggregate coverage includes missing rows.
| Recipient | Current balance | First position | Receipt references |
|---|
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 graph1 wallets · 0 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.
HTG4jCTAVB6H8QThytKtrApjNaQhMuUENFi9Whppag6Z
Creator attribution
Balance at last observation
Unknown
Time unavailable · observation, not a live balance
No transaction reference was stored for this wallet. No relationship is inferred.
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.
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-18 00:45:45 UTC · Funding research runs only when requested.
Rug.Tools analysis
Rug.Tools analysis
Multiple health signals are weakening, and one holder account holds 14.3% of supply, and sampled holder accounts hold 39.0% of supply, and liquidity is very thin, so trades will move the price sharply.
Verdict from canonical snapshot e58e3808 · v3 · scanned 2026-10-18 00:45 UTC · page content updated 2026-10-18 00:45 UTC
Holder distribution
Holder distribution
Creator profile
Creator profile
HTG4jCTAVB6H8QThytKtrApjNaQhMuUENFi9Whppag6ZToken activity
Token activity
- 2026-10-17 23:16 UTCToken launchedFirst on-chain trading pair opened on meteora.
- 2026-10-18 00:45 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 PumpOnboard?⌄
PumpOnboard 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 PumpOnboard safe?⌄
Current Rug.Tools verdict: Elevated Risk. Multiple health signals are weakening, and one holder account holds 14.3% of supply, and sampled holder accounts hold 39.0% of supply, and liquidity is very thin, so trades will move the price sharply. 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 PumpOnboard have?⌄
Rug.Tools currently sees 166 holders. The largest holder account holds 14.28% of supply; the top 10 holder accounts together hold 38.97%. These balances alone do not establish individual ownership or independent control.
Where is PumpOnboard traded?⌄
The primary trading venue detected on Solana is meteora. 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.