Trading activity:
Reported 24-hour volume equals 0.00% of market capitalization. The local markets snapshot lists Raydium among venues with observed trading activity.
Values are descriptive and should be read together rather than as a price forecast.
Read the YearBull methodology.
Snapshot date: 2026-09-12.
Methodology responsibility:
YearBull’s analytical methodology and presentation rules are developed and maintained by
Alan Zelvin, Founder & Lead Crypto Researcher.
This note identifies responsibility for the methodology; it does not attribute authorship of this data snapshot.
Latest available YearBull Rank for wifejak: #3438.
Rank timeline (last 365 days)
Rank movement (time windows).
Reading rule: lower is better in this ranking.
7d window (2026-09-05): #3722 → #3438 (up by 284).
30d window (2026-08-13): #2555 → #3438 (down by 883).
YearBull Rank is a comparative ordering used on YearBull to place a coin versus others using a consistent set of inputs. Lower rank numbers indicate stronger placement in the current snapshot.
Phase read: If the 30d is noisy, increase the lookback to avoid over-reading. cycle pressure can surface as slow bleed in rank.
Trading footprint: If rank deteriorates while the curve stays smooth, it can be cohort strength shifting. consolidation can make rank more stable.
Liquidity angle: If the line only moves on high-volume days, liquidity is a key filter. relative rank is sensitive to who is active in the window.
Volatility posture: If it is flat for long, the coin may be tracking the cohort. range behavior tells more than a single point.
Editorial note:
This analysis was prepared by the YearBull research team under the direction of
Alan Zelvin,
Founder and Lead Crypto Researcher.
The assessment follows YearBull’s internal research methodology and editorial standards.
Methodology ·
Editorial Policy
We use cookies and similar technologies to improve site functionality, analyze usage, and enhance user experience.
By continuing to use YearBull, you agree to our use of cookies as described in our
Privacy Policy.
Comments