RUG.TOOLSLargest Robbery$ROBBERY
Risk analysis for Largest Robbery (ROBBERY) on Solana — contract AdkZmHCBtJyDv1GmYA93JZTG7rts3B7heMrVvayVpump. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Total tracked liquidity
$26,831.89
Combined across tracked pools. Individual pools can have much less liquidity; the total is not an executable exit quote.
Market snapshot · · Snapshot values are not live quotes.
Compare tracked pools (2)
- pumpswap · PrimaryDNEtCdf…TbLzD ↗$26,831.89
- pumpfun31qdnnr…erHbC ↗Not recorded
Scanned 2026-10-30 03:41 UTC
- 1.Historical launch exposure
Sampled launch-wallet exposure reached up to 83.27% of supply during the launch window across 34 tracked wallets. The token is actively trading, but a launch-pattern cohort had reported historical exposure of 83.3% of supply; this may include creator allocations and transfers, not just purchases, and independent wallet linkage is not fully corroborated.
Why it matters: This is historical exposure, not current ownership. The sampled pattern does not prove shared funding, insider control, or executed bundled purchases.
- 2.Current launch-wallet balances
0.00% of supply measured across 34/34 tracked launch wallets at the recorded observation.
Why it matters: Current balances and historical launch exposure measure different moments. Unmeasured wallet balances are unknown; related wallets are not automatically one owner.
- 3.Reported liquidity depth
$26,831.89 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.
See 2 additional recorded findings
- 4. Top 10 individual wallet concentration
The reported top 10 individual wallets hold 5.91% 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.
- 5. Creator wallet holdings
The identified creator wallet has 0.00% 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.
• 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.
• Launch-pattern confidence does not verify funding relationships, common ownership or bundle execution.
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 provider unavailable — showing last verified values from 19 hours ago.
Market data
Trading activity
Markets & liquidity pools
Markets & liquidity pools
Primary indexed pool
DNEtCdf1eky8xX78aR7tRBsEai67yx5FVQigCFkTbLzDThe page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is Largest Robbery?
What is Largest Robbery?
Largest Robbery ($ROBBERY) is a SPL token on the Solana blockchain Its primary trading venue is pumpswap, with roughly $26.83K in live on-chain liquidity. It currently has 735 on-chain holders, and was first traded new (today). Rug.Tools' current assessment of Largest Robbery 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
- 0.00%
- Historical launch exposure
- 83.27%
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
35 observed recipients
Interval evidence only; full launch coverage is reported separately.
38 receipts examined
Current cohort balances
0.00%
34/34 wallets measured · 0 unknown
Custody coverage
1 custody accounts / markets
1 without verified protection
Token custody and LP withdrawal protection are separate checks.
Creator provenance
83pJSt…yQRR · 0.00% current measured holdings
Attribution: mint_transaction. Identified wallet only; this does not establish total team ownership.
Launch timeline & receipt references
Anchor slot #463,129,653 · observed through #463,129,678 · Reconstruction captured:
| From anchor | Recipients | Net inflow / supply | Evidence |
|---|---|---|---|
| +0 slots | 13 | 81.93% | Stored interval verified |
| +2 slots | 25 | 82.97% | Stored interval verified |
| +5 slots | 30 | 83.16% | Stored interval verified |
| +10 slots | 34 | 83.27% | Stored interval verified |
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.
- 1k6kMN…5NN7 · #463,129,653
- 2W7iBg…kAhE · #463,129,653
- 31gXCP…jyBs · #463,129,653
- 3VBXiS…1Qmr · #463,129,653
- 67LNPn…EdvL · #463,129,653
- 176VGT…H1dL · #463,129,654
- 2bQA6a…mVUu · #463,129,654
- 2J5yxQ…hBoK · #463,129,654
- 2wz7hz…N2Yw · #463,129,654
- 2Yg817…RjDH · #463,129,654
- 31CLmS…D4a3 · #463,129,654
- 3fVCBr…apdw · #463,129,654
- 4D3rc4…aXWN · #463,129,654
- 4GbAF3…K8bU · #463,129,654
- 4T7JoG…fhxo · #463,129,654
- 5d1WRg…Lri6 · #463,129,654
Pool-by-pool custody & protection
14.21% of token supply in custody · reported role / market · vault CXppMF…ycZJ
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 34 stored sample rows are listed; aggregate coverage includes missing rows.
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 · 24 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.
83pJStnq2a7dvdT7WqL2VGd38jUSDgQ9SgXSPSP5yQRR
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.
Creator balance history
2026-10-30 03:21:01 UTC · previous mint write
Exact on-chain amounts
0 / 969713960217898 raw units
Checkpoints show historical balances. A reduction does not establish a sale. Launching multiple tokens does not establish malicious intent.
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-30 03:41:03 UTC · Funding research runs only when requested.
Rug.Tools analysis
Rug.Tools analysis
The token is actively trading, but a launch-pattern cohort had reported historical exposure of 83.3% of supply; this may include creator allocations and transfers, not just purchases, and independent wallet linkage is not fully corroborated.
Verdict from canonical snapshot 03788090 · v3 · scanned 2026-10-30 03:41 UTC · page content updated 2026-10-30 03:40 UTC
Holder distribution
Holder distribution
Creator profile
Creator profile
83pJStnq2a7dvdT7WqL2VGd38jUSDgQ9SgXSPSP5yQRRToken activity
Token activity
- 2026-10-30 03:15 UTCToken launchedFirst on-chain trading pair opened on pumpswap.
- 2026-10-30 03:40 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 Largest Robbery?⌄
Largest Robbery 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 Largest Robbery safe?⌄
Current Rug.Tools verdict: Elevated Risk. The token is actively trading, but a launch-pattern cohort had reported historical exposure of 83.3% of supply; this may include creator allocations and transfers, not just purchases, and 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 Largest Robbery have?⌄
Rug.Tools currently sees 735 holders. The largest holder account holds 0.65% of supply; the top 10 holder accounts together hold 5.91%. These balances alone do not establish individual ownership or independent control.
Where is Largest Robbery traded?⌄
The primary trading venue detected on Solana is pumpswap. 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.