| Icon | Applied rules* | What this means in fact |
|---|---|---|
| 🦄 | R >= 50 (any S/L) | ✨🌈 Rocks! The perfect scenario, definitely with a excellent download speed 🚀 and a life as a 🦄 |
| 🌕 | ThresholdsByRange** | ☀️ Excellente availability, with probably a good to very good download speed 🐇 and download will have a solid life 💖 |
| 🌖 | ThresholdsByRange** | 🌤 Good availability, with probably a medium to good download speed 🐎 and download probably will have a good life ❤️ |
| 🌗 | ThresholdsByRange** | 🌦 Medium availability, with probably a slow to medium download speed 🐪 and download may will be complicated or not possible ⛓️💥 in middle term ⏳ |
| 🌘 | ThresholdsByRange** | 🌧 Acceptable availability, with probably a very slow to slow download speed 🐄 and download may will not be possible ⛓️💥 in short or middle term ⌛ |
| 🌑 |
ThresholdsByRange (S == 1 || 2) && L == 0 |
❄️ Poor availability, with definitely slower speed 🐢 and download may will not be possible ⛓️💥 in (very) short term ⌛ |
| 🌑❗ | S == 2 && L > 0 | Wanted ❗ but slower ❄️ and download may will not be possible ⛓️💥 in very short term ⌛ |
| 🌑 ⁉️ | S == 1 && L > 0 | Wanted ❗, but completion is uncertain ❓ download and can breakdown ⛓️💥 at any time 🪫 |
| 💀‼️ | S == 0 && L > 0 | Wanted, but dead ‼️ |
| 💀 | S == 0 && L == 0 | Just dead (not seeded), and not wanted (leeched) for now |
| ❔ | isNaN(S) || isNaN(L) | Can't calculate (no proper input value) |
1️⃣ ThresholdsByRange: definition of availability ratio thresholds ({...}) by seeders number range (1st value):
3-4: { acceptable: 0.50, medium: 2.0, good: 4.0, excellent: 6.0 }
5-6: { acceptable: 0.35, medium: 0.8, good: 2.0, excellent: 4.0 }
7-9: { acceptable: 0.30, medium: 0.6, good: 1.5, excellent: 3.5 }
10+: { acceptable: 0.25, medium: 0.5, good: 1.5, excellent: 3.0 }
2️⃣ Find matching range by number of seeders:
If S<=4, so range = '3-4'
if else S<=6 ? '5-6'
if else S<=9 ? '7-9'
else '10+';
3️⃣ Get corresponding range's thresholds:
rangeThresholds = ThresholdsByRange[range] (1️⃣[2️⃣]):
4️⃣ Compare to availability ratio (R > 3️⃣.threshold):
R > rangeThresholds.excellent 🌕
R > rangeThresholds.good 🌖
R > rangeThresholds.medium 🌗
R > rangeThresholds.acceptable 🌘
R < rangeThresholds.acceptable 🌑
This is a vilgarization of the code. For more details, see source code.
| Tracker | Announcement | Minimal |
|---|---|---|
| udp://tracker.opentrackr.org:1337 🇳🇱 | 30 min | ? |
| udp://open.stealth.si:80 🇳🇴 | 30 min | ? |
| udp://tracker.torrent.eu.org:451 🇫🇷 | 30 min | ? |
| udp://tracker.srv00.com:6969 🇸🇪 | 30 min | ? |
| udp://tracker2.dler.org:80 🇹🇼 | 30 min | ? |
| udp://p4p.arenabg.com:1337/announce 🇧🇬 | 30 min | ? |
| udp://tracker.qu.ax:6969/announce 🇫🇷 | 30 min | ? |
| udp://martin-gebhardt.eu:25/announce 🇩🇪
udp://martin-gebhardt.eu:80/announce 🇩🇪 udp://martin-gebhardt.eu:6969/announce 🇩🇪 |
30 min | ? |
(¹) About Seeders and Leechers, it's values declared on the trackers for last few minutes, varies by tracker... Each tracker set its own default announcement interval for connected clients, usually of 30 min, but can be from 15 to 60 min for the most cases.
So, Health / Availability is a estimation for the last period: is calculated based on these values, potentially innaccurate. This is especially true if the base values are low, which relates a relative and significant amplitude of change.
(²) Completed downloads values are not accurate for all torrents life. On main public trackers, theses stats are not persistent (RAM stored). So, theses volatile data can therefore disappear depending on the frequency of service interruptions (routine maintenance, breakdown, etc.). They give a trend only, but absolutely not representative in the medium or long term.