FREDDY holder count
4Aug 24, 2026 20:09 UTC · One recorded value
getProgramAccounts · holder_count_measured · getProgramAccounts. More dated values are needed to chart a trend.Watchlist, recently viewed tokens, and since-last-visit snapshots follow this account. Nothing is emailed.
Solana · No market returned by the checked sources
Saved market observation: Not recorded. Refreshes when you visit.
·
Current quotes are separate from the historical report below. Volume and liquidity describe the displayed pool; unavailable fields are not zero.
FREDDY was archived on August 24, 2026 because 18 catalog lookup checks did not retain a qualifying market for its Solana contract.
Solana · B4NJKm3DjsuuSmBFSEXUT7qLfcb5c9p7ZSkwPqpEXgYY
Latest dated evidence:
FREDDY has 1 dated snapshots and 0 daily candles in this archive. Explore each available source and pool below.
Aug 24, 2026 20:09 UTC · One recorded value
getProgramAccounts · holder_count_measured · getProgramAccounts. More dated values are needed to chart a trend.Aug 24, 2026 20:09 UTC · One recorded value
getProgramAccounts · measured_top10_pct · getProgramAccounts. More dated values are needed to chart a trend.FREDDY chain snapshot: August 24, 2026. Account shares can include pools and custodians.
Entered the DexBrief catalog.
no tracked market after 18 checks
No market returned by the checked sources
First tracked is not launch; retirement is a catalog decision, not a verified final trade or cause of death.
For FREDDY, the stored decision is "no tracked market after 18 checks". The record counts 18 checks, but does not retain 18 independent provider responses. It cannot establish the date of FREDDY's last trade.
The August 24, 2026 FREDDY snapshot records 4 measured holder entries through getProgramAccounts. It separately reports 6 token accounts; that account count is not a count of unique owners. 2 entries exceeded 0.01% of FREDDY supply. That is 50.0% of the measured holder entries; the remainder held smaller balances. The measured top-ten entries represented 100.00% of supply in that snapshot. The FREDDY concentration figure does not identify which large entries belong to pools, custodians or individual people. With fewer than ten recorded entries, FREDDY's remaining holder base is especially narrow in this source snapshot.
FREDDY's August 24, 2026 contract snapshot records mint authority: revoked; freeze authority: revoked; token supply: 5,804,031.4793. The tracked deployer held 0.0000% of FREDDY supply at that check. A zero FREDDY balance does not show when or how those tokens left that address.
At the September 17, 2026 follow-up for FREDDY, the results were DexScreener: empty; GeckoTerminal: empty. No matching FREDDY market was returned by these completed checks.
The FREDDY archive currently contains 1 dated snapshot(s) and 0 daily candle(s). It lacks a comparable price or activity series spanning at least six hours. First tracking is June 09, 2026; catalog retirement is August 24, 2026. An observed decline between those markers cannot be reconstructed from the retained FREDDY values alone.
| Source | Result | Checked (UTC) | Pools returned | Evidence |
|---|---|---|---|---|
| DexScreener | empty | 2026-09-17 10:28 UTC | 0 | exact_contract_lookup |
| GeckoTerminal | empty | 2026-09-17 10:29 UTC | 0 | exact_contract_lookup |
Each row is one source and one scope. Pool liquidity and activity are not token-wide totals. Missing fields are not zero. Full history is available in the downloads.
| Observed (UTC) | Source | Scope / exact pool | Price | Liquidity | 24h volume | 24h trades |
|---|---|---|---|---|---|---|
| 2026-08-24 20:09 UTC | getProgramAccounts | getProgramAccounts | Not recorded | Not recorded | Not recorded | Not recorded |
DexBrief. “FREDDY: retirement and market activity report.” Evidence checked 2026-09-17T10:29:05+00:00. Methodology 2.1. https://dexbrief.com/graveyard/reports/freddy-3c34ec8ce5684d9aeef7/
DexBrief’s compiled observations and analysis may be cited with attribution under CC BY 4.0; underlying provider data remains subject to its source terms.
Evidence SHA-256: 5bb1021a73d519ed638bd7b9b0496b777111b0ae68f4667e8e2ce943437ce684