RUG.TOOLS
Not In Labor Force$NILF
Risk analysis for Not In Labor Force (NILF) on Robinhood — contract 0xdb97b2aefd6816485a757ae49280d598a5c9c848. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Scanned 2026-10-01 07:20 UTC
The token is actively trading, but new tokens can be minted.
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
0x08eb047c87b25e52936fd60201e74aaf385706bace2ecb2df3d6b9c3f4fff174The page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is Not In Labor Force?
What is Not In Labor Force?
Not In Labor Force ($NILF) is a ERC-20 token on the Robinhood blockchain Its primary trading venue is uniswap, with roughly $127.96K in live on-chain liquidity. It currently has 1,025 on-chain holders, and was first traded 1 month old. Rug.Tools' current assessment of Not In Labor Force is "Use Caution", 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
The token is actively trading, but new tokens can be minted.
Verdict from canonical snapshot f0ae23d5 · v3 · scanned 2026-10-01 07:20 UTC · page content updated 2026-10-01 07:20 UTC
Holder distribution
Holder distribution
Creator profile
Creator profile
0x84b8affbd7728217f97c8eb47fe4bda07d97b8c1Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
Token activity
- 2026-08-30 08:48 UTCToken launchedFirst on-chain trading pair opened on uniswap.
- 2026-10-01 07:20 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 Not In Labor Force?⌄
Not In Labor Force 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 Not In Labor Force safe?⌄
Current Rug.Tools verdict: Use Caution. The token is actively trading, but new tokens can be minted. 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 Not In Labor Force have?⌄
Rug.Tools currently sees 1,025 holders. The largest holder account holds — of supply; the top 10 holder accounts together hold —. These balances alone do not establish individual ownership or independent control.
Where is Not In Labor Force 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.