Risk view
Lower risk
Low liquidity
Live token report
BSC | 0x4aCb4CC1f0A073ce4BDe893fAebc726198c14444
Track the exact Nasdaq666 token address, live risk score, current status, liquidity, trading activity, and related scanner pages on FreshTokenWatch.
Risk view
Low liquidity
Health view
There is some real activity, but the market picture is not strong enough to treat as stable.
Risk score
38/100
Lower risk
This is the current risk snapshot from the latest crawl. Lower is better. It reacts to liquidity, transaction activity, volume, valuation balance, and detected red flags.
Health score
50/100
Mixed market profile
There is some real activity, but the market picture is not strong enough to treat as stable. This score uses the latest available liquidity, 24h volume, 24h transactions, token age, and current risk score.
Price
$0.000019
Liquidity
24.91K
24h volume
71.39K
24h transactions
313
Last seen
7h ago
A few hours old
Quick verdict
Needs confirmation
Risk 38 / Health 50There is some activity here, but not enough strength to trust the setup without extra checks on liquidity, volume, and recent status changes.
Best next action
Open explorer and verify contract behavior
Most important signal
Low liquidity
Use these as the immediate next checks before trusting the token.
Liquidity is thin
Wait for deeper liquidity before trusting price action. Thin pools can move violently and are easier to manipulate.
Review the flagged risk signals
The crawler already detected low liquidity. Open the explorer and pair page before assuming the setup is clean.
Nasdaq666 (NDQ) is a 279d old token on BSC with token address 0x4aCb4CC1f0A073ce4BDe893fAebc726198c14444, risk score 38, and active status. FreshTokenWatch currently tracks 313 recorded 24h transactions, liquidity around $24.9K, and 24h volume near $71.4K.
Key concern
Current market signals look comparatively stronger than the average fresh launch, but this is still a fast-moving token.
Signal
Low liquidity
Token address
0x4aCb4CC1f0A073ce4BDe893fAebc726198c14444
Token ID
bsc__0x4acb4cc1f0a073ce4bde893faebc726198c14444
Status
Pair age
9 months
Source
dexbackfill
Seen
7h ago
Record updated
7h ago
The main internal routes for this token. Each link appears only once to keep the page cleaner.
Latest crawler sighting
7h ago
This is the last time the crawler refreshed the market snapshot for this token.
Record state
A few hours old
Published tokens stay visible in the database even when live activity weakens or disappears.
Multiple pools are stored per token. The scanner prefers pools with real trade activity before a token is surfaced.
Mar 20, 2026, 10:04 AM to Apr 16, 2026, 3:10 AM (46 recorded snapshots)
This is not a live candle chart. It shows how the risk score changed across the most recent stored crawls.
Green dots mean active, yellow warning, red dead.
Created
Jul 10, 2025, 2:59 PM
Published
Mar 20, 2026, 10:04 AM
FDV
19.2K
FDV / liquidity
0.77x
These glossary pages explain the exact risk and market terms that matter for this token report.
Token Address
Using the wrong token address is one of the fastest ways to buy the wrong asset or a copycat contract.
Risk Score
It helps prioritize review, but is not investment advice.
Trading Volume
Volume helps distinguish real market interest from inactive or abandoned pairs, though it can still be manipulated.
Liquidity Pool
Pool depth affects slippage, execution quality, and whether a token has a real market at all.
Liquidity Lock
A lock is a positive signal, but not a full security guarantee.
NDQ666 (NDQ)
BSC • Risk 62 • Vol 0.07
Address: 0x1A1d1980548fa30c69e90c744Ce939dF73F81473
NDQ666 (NDQ) is a 50d old token on BSC with token address 0x1A1d1980548fa30c69e90c744Ce939dF73F81473, risk score 62, and warning status. Fre
NDQ666 (NDQ)
BSC • Risk 62 • Vol 0.07
Address: 0xaC16e818500f4d11feD898344EF85ceFd7C3Ce49
NDQ666 (NDQ) is a 51d old token on BSC with token address 0xaC16e818500f4d11feD898344EF85ceFd7C3Ce49, risk score 62, and warning status. Fre
R2 Protocol (R2)
BSC • Risk 26 • Vol 777.51M
Address: 0xFCD1B7CAFedFD5C54cCC6Eb7aFdF113E6b75f43F
R2 Protocol (R2) is a 21h old token on BSC with token address 0xFCD1B7CAFedFD5C54cCC6Eb7aFdF113E6b75f43F, risk score 26, and active status.
Binance Ai Pro (Binance Ai Pro)
BSC • Risk 34 • Vol 605.72M
Address: 0x2a32F0E2F0496797f2fCd5034eeDC93fA70Ddd6c
Binance Ai Pro (Binance Ai Pro) is a 0h old token on BSC with token address 0x2a32F0E2F0496797f2fCd5034eeDC93fA70Ddd6c, risk score 34, and a
TMM (TMM)
BSC • Risk 40 • Vol 542.55M
Address: 0x1d6F03B0B20b2EC05b37bF60F56af442Ced66666
TMM (TMM) is a 25d old token on BSC with token address 0x1d6F03B0B20b2EC05b37bF60F56af442Ced66666, risk score 40, and active status. FreshTo
quq (quq)
BSC • Risk 16 • Vol 428.57M
Address: 0x4fa7C69a7B69f8Bc48233024D546bc299d6B03bf
quq (quq) is a 291d old token on BSC with token address 0x4fa7C69a7B69f8Bc48233024D546bc299d6B03bf, risk score 16, and active status. FreshT
Binance Ai Pro (Binance Ai Pro)
BSC • Risk 44 • Vol 399.32M
Address: 0x112B40Ae5e5585aD05379559489098EC0C749800
Binance Ai Pro (Binance Ai Pro) is a 17h old token on BSC with token address 0x112B40Ae5e5585aD05379559489098EC0C749800, risk score 44, and
AI小何 (AI小何)
BSC • Risk 44 • Vol 92.65M
Address: 0x57415C5357E0b0cD19425bf2683681E40B24fE4f
AI小何 (AI小何) is a 17h old token on BSC with token address 0x57415C5357E0b0cD19425bf2683681E40B24fE4f, risk score 44, and active status. Fresh
The tracked NDQ token address on BSC is 0x4aCb4CC1f0A073ce4BDe893fAebc726198c14444. FreshTokenWatch shows the exact contract address in the page content so users can verify they are looking at the right token.
NDQ currently has a FreshTokenWatch risk score of 38/100 and a active status. That is not an endorsement or a guarantee. It is a live scanner snapshot based on liquidity, volume, activity, valuation balance, and current red flags. The main concern right now is low liquidity
Verify the token address 0x4aCb4CC1f0A073ce4BDe893fAebc726198c14444, compare the token against the scanner history, review liquidity and 24h transaction activity, and open the external explorer or DEX pair pages before acting.
Browser notifications are not supported here.
Add tokens from the token page to start alerts.
Open another token page and it will appear here.