Alert Outcome Analysis — May 5, 2026

Summary: This batch tested 63 post-migration alerts that were generally called around the 34K market-cap zone. The main question was whether these alerts ever offered a profitable post-alert exit window, which trader-count buckets performed best, and whether migration-speed tier helped separate runners from weak alerts.

Period: May 5, 2026 PT
Total alerts: 63
Winner definition: post-alert ATH reached at least 2x the alert market cap
Entry assumption for simulations: 0.05 SOL per alert
Sources: enriched alert CSV generated from DexScreener current MC/FDV and GeckoTerminal minute OHLCV
Confidence: 61 high-confidence rows, 2 medium-confidence rows


Core Results

ThresholdAlerts HitRate
1.5x+ post-alert37 / 6358.7%
2x+ post-alert23 / 6336.5%
5x+ post-alert5 / 637.9%
10x+ post-alert2 / 633.2%

The batch had a decent number of tradable 2x opportunities, but true runners were rare. Only 5 alerts reached 5x+, and only 2 reached 10x+.


Top Post-Alert Runners

RankTokenTierTradersTrader NamesAlert Time PTCurrent MC/FDVPost-Alert ATH MCMax MultipleATH Time PT
1SELLOR / Michul SellorMODERATE2trenchman, cupsery2026-05-05 03:22 PM495K858K24.15x2026-05-05 06:02 PM
2wrdog / World Record DogFAST1chester2026-05-05 02:53 AM89K538K16.87x2026-05-05 05:30 AM
3Alzheimers / Buy & ForgetMODERATE2decu, parsiix2026-05-05 07:50 PM176K286K8.62x2026-05-05 10:27 PM
4AI / Artificial InuFAST1casino2026-05-05 11:50 AM74K211K6.69x2026-05-05 06:54 PM
5AI / Artificial InuFAST3dv, bandit, casino2026-05-05 11:50 AM14K216K6.24x2026-05-05 02:30 PM
61 / 1 min a daySLOW1cupsery2026-05-05 09:40 AM3K137K4.66x2026-05-05 09:47 AM
7turdcoin / turdcoinEXTREME1nyhrox2026-05-05 05:58 AM24K141K4.34x2026-05-05 06:01 AM
8LUKE / Luke Battles Cancer FundSLOW1parsiix2026-05-05 10:06 AM4K142K4.26x2026-05-05 12:02 PM
9LOBBYOOR / Bitcoin Policy InstituteMID1cupsery2026-05-05 11:02 PM58K146K4.07x2026-05-05 11:16 PM
10Roho / RohoMODERATE1nyhrox2026-05-05 08:19 AM6K91K3.31x2026-05-05 08:41 AM

Results by Migration-Speed Tier

TierSpeed BucketAlerts2x+ Winners2x Win Rate5x+ RunnersMedian Max Multiple
EXTREME0-1.5m22731.8%01.72x
VERY_FAST1.5-3m3133.3%01.37x
FAST3-5m11436.4%31.59x
MODERATE5-10m12541.7%21.35x
MID10-15m9333.3%01.71x
SLOW15-20m6350.0%02.13x

Tier Takeaways

  • FAST and MODERATE produced every 5x+ runner in this batch.
  • SLOW had the highest 2x win rate, but no 5x+ runners.
  • EXTREME had the most alerts and many small wins, but none reached 5x+.
  • MID produced some tradable moves, but no main runners.

Interpretation: fastest migration was not automatically best. The strongest runners clustered in the middle speed bands, especially FAST and MODERATE.


Results by Trader Count

TradersAlerts2x+ WinnersWin RateSold ATH PnLSell 2x PnLStill Holding PnL
1361438.9%+2.901 SOL-0.289 SOL-1.080 SOL
215746.7%+2.130 SOL-0.012 SOL+0.275 SOL
39111.1%+0.406 SOL-0.319 SOL-0.399 SOL
43133.3%+0.088 SOL-0.032 SOL-0.121 SOL

Simulation assumptions:

  • Every alert receives a 0.05 SOL entry.
  • “Sold ATH” assumes perfect exit at post-alert ATH.
  • “Sell 2x” assumes a position is sold at exactly 2x if it reaches 2x; otherwise it is marked at current value.
  • “Still Holding” marks every alert at current value from the enriched CSV.

Trader-Count Takeaways

  • 2-trader alerts had the best 2x win rate at 46.7%.
  • 1-trader alerts still produced 14 winners and 2 of the 5 main runners.
  • 3-trader alerts underperformed badly in this batch: 1 winner out of 9.
  • More traders did not automatically mean better alert quality.

Important refinement: 2+ traders is a useful signal, but it is not mandatory for runners. The largest two outcomes were split: SELLOR had 2 traders, while wrdog had only 1 trader.


Portfolio Simulation — 0.05 SOL Per Alert

StrategyFinal ValuePnL
Spend 0.05 SOL on all 63 alerts3.150 SOL cost—
Sell every alert at post-alert ATH8.674 SOL+5.524 SOL
Sell at 2x when reached, otherwise hold current2.498 SOL-0.652 SOL
Still holding all positions1.825 SOL-1.325 SOL

The perfect-ATH strategy was strongly profitable, but this is not executable in practice. The mechanical 2x strategy lost money because the losers and current marks outweighed the capped winners. Still holding the full batch was worse.

Key implication: this alert stream can identify tokens that eventually move, but exit quality matters heavily. Capturing runners requires either a trailing strategy or a better rule for filtering losers before entry.


Results by Time of Day

DaypartAlerts2x+ Winners5x+ RunnersMedian Max Multiple
Overnight10311.56x
Morning221021.93x
Afternoon20511.39x
Evening11511.82x

Morning had the highest count of 2x+ winners and the best median multiple. However, 5x+ runners appeared across multiple dayparts, so time of day is a secondary filter, not a standalone rule.


Pattern Notes

Pattern 1 — FAST and MODERATE produced the main runners

All 5 alerts that reached 5x+ came from FAST or MODERATE tiers. This suggests the best runner zone in this batch was not the absolute fastest migration bucket. EXTREME generated many alerts and several 2x wins, but no 5x+ outcomes.

Rule candidate: prioritize FAST and MODERATE when looking for main runners, but do not fully discard SLOW because it had a high 2x hit rate.

Pattern 2 — 2 traders was the best consensus bucket

2-trader alerts had the highest win rate at 46.7% and included 2 of the top 3 runners: SELLOR and Alzheimers. This supports the idea that light consensus can improve signal quality.

But 1-trader alerts still mattered. wrdog, AI, turdcoin, LUKE, LOBBYOOR, and Roho were all 1-trader alerts in the top 10.

Rule candidate: require 2+ traders only if the goal is consistency. Do not require 2+ traders if the goal is catching all main runners.

Pattern 3 — 3+ traders did not confirm quality

3-trader alerts produced only 1 winner out of 9. The 3-trader AI row was a runner, but the bucket overall was weak. This contradicts a simple “more traders = better” thesis for this day.

Rule candidate: treat 3+ traders as a context signal, not an automatic entry. Pair it with tier, narrative quality, and trader identity.

Pattern 4 — Holding was structurally weak

Still holding all 63 alerts would be down 1.325 SOL on a 3.15 SOL deployment. This is important because many alerts did become profitable at some point, but later gave back value.

Rule candidate: alerts are better treated as trade opportunities than long holds unless the token is showing unusual continuation strength.

Pattern 5 — Mechanical 2x sells were not enough

Selling every 2x hit at exactly 2x still lost 0.652 SOL if all non-2x alerts were held to current value. This means the strategy needs either:

  • tighter invalidation on losers,
  • partial exits plus trailing winners,
  • better entry filtering,
  • or a rule that avoids buying every alert.

Working Rules to Test Next

  1. Prioritize FAST and MODERATE for runner hunting.
  2. Keep 1-trader alerts eligible if the trader is high quality or the narrative is strong.
  3. Treat 2-trader alerts as the strongest default consensus bucket in this sample.
  4. Do not assume 3+ traders means higher quality.
  5. Avoid “buy all and hold” behavior.
  6. Test a rule that takes partial profit at 2x but lets a runner portion trail.
  7. Separate “tradable 2x opportunity” from “main runner candidate” in future tagging.

Synopsis Lesson — TP Strategy

The May 5 dataset does not support buying every alert blindly. Across all 63 alerts, fixed full-position take-profits from 1.25x to 10x were not profitable when misses were marked at current value. The edge appeared only after filtering the alert set first.

The strongest filter from this batch was FAST/MOD with 1-2 traders. That subset had 17 trades, with 0.85 SOL deployed at 0.05 SOL per alert.

Strategy Comparison — FAST/MOD + 1-2 Traders

These simulations mark unsold bags at current value from the enriched CSV.

StrategySimulated PnLROI
25% at 3x, 25% at 5x, 25% at 10x, 25% hold/current+0.466 SOL+54.8%
Sell 33% at 3x, hold 67% current+0.441 SOL+51.9%
33% at 3x, 33% at 6x, 34% hold/current+0.435 SOL+51.2%
50% at 2.5x, 50% hold/current+0.394 SOL+46.3%
Sell full at 5x+0.381 SOL+44.8%
50% at 3x, 50% hold/current+0.360 SOL+42.4%

Preferred Operating Strategy

RuleSetting
Entry filterFAST or MODERATE tier
Trader count1-2 traders
Position size0.05 SOL
First take-profitSell 25% at 3x
Second take-profitSell 25% at 5x
Runner take-profitSell 25% at 10x
Final 25%Trail or hold only while momentum is alive
Risk controlCut dead trades early; do not hold full bags to zero

Lesson: do not sell too close to 2x as the main plan. A 2x TP leaves too much upside behind and still did not cover the full unfiltered book. In this batch, the better structure was to filter hard first, then let winners breathe. First initials at 3x, not 2x, with a runner ladder at 5x and 10x.

Risk note: the stop/failed-exit simulations were directionally useful but optimistic because this CSV contains post-alert ATH and current value, not the exact intratrade low path. Treat the 3x/5x/10x ladder as the working hypothesis to test, not a final proven rule.


Change Log

  • 2026-05-06: Created new standalone analysis page from the final enriched May 5 alert CSV. Existing wiki pages were not modified.
  • 2026-05-06: Added TP strategy synopsis from threshold simulations. Main lesson: avoid buying every alert; prefer filtered FAST/MODERATE 1-2 trader entries with 2.5x as the primary take-profit.
  • 2026-05-06: Updated TP strategy after broader comparison. Main lesson shifted from 2.5x primary TP to filtered FAST/MOD 1-2 trader entries with first initials at 3x and a 5x/10x runner ladder.