Trading activity:
Reported 24-hour volume equals 57.71% of market capitalization. The local markets snapshot lists LBank, MEXC and BingX 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.
YearBull Rank now for broadcom-ondo-tokenized-stock: #1715.
Rank timeline (last 365 days)
Rank change (nearest points).
Reading rule: smaller rank numbers are better.
7d window (2026-09-05): #2165 → #1715 (up by 450).
30d window (2026-08-13): #2101 → #1715 (up by 386).
YearBull Rank is an internal ordering on YearBull that positions a coin relative to the rest of the tracked universe. Treat it as a directional context tool rather than a standalone verdict.
Regime context: If the line stair-steps, the cycle may be driven by discrete inputs. a stable phase often tightens the rank range.
Trading footprint: If the line breaks range, confirm it across a longer window. changes can follow how the coin is routed across markets.
Flow context: If the curve improves and holds, it is usually more structural. relative rank is sensitive to who is active in the window.
Risk note: If you see repeated snap-backs, assume sensitivity to one factor. 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