"디너파티를 위한 클래식" Chart Performance Analysis
Playlist by Apple Music Classical
Executive Summary
AI-generated performance analysis
Average
This playlist achieves a C+ (Average) chart performance rating, peaked at #61.
"디너파티를 위한 클래식" by Apple Music Classical demonstrates moderate chart performance on Apple Music.
The playlist has spent 38 days on the Top 100 chart.
- Peak: #61
- 38 days on chart
- Curator: Apple Music Classical
Performance Factors Analysis
Breakdown of key metrics driving performance
Chart Performance
Peak position achieved on the charts
- Peak position: #61
- Peak date: Feb 16, 2026
Chart Longevity
Total duration on the charts
- 1.3x longer than average playlist
- 38 total days on chart
- 25 max consecutive days
Chart Stability
Consistency of chart position
- Very stable chart performance
- Stability index: 85/100
Current Momentum
Recent chart movement trend
- Stable chart position
- Consistent performance
Moderate performance. Some factors could be stronger.
Benchmark Comparison
Performance compared to Apple Music Playlist Average average
22% below avg
1.3x higher than avg
1.7x higher than avg
Above average performance compared to Apple Music Playlist Average content.
Ranking History & Insights
Performance over time
Currently ranked #88. Peak was #73. Ranking is stable.
Peak reached on Sep 6, 2026
Current Streak
13d
Best: 25d
Avg Position
#80.5
Last 30 days
7-Day Trend
—
Stability
—
Apple Music Reference
Source content being analyzed
디너파티를 위한 클래식
Apple Music Classical
points
Ranked #249 all-time
About Rankings
Rankings are based on Apple Music Top 100 charts in South Korea. Updated daily.
About This Analytics Report
This report is generated by Top1Trend's analytics engine, which tracks Apple Music trending data across 30+ regions since 2024. All metrics are derived from official chart positions via the official Apple Music API.
Top1Trend is an independent analytics service and is not affiliated with, endorsed by, or sponsored by Apple Music. All trademarks belong to their respective owners. Data accuracy depends on platform API availability and may have slight delays from real-time values.