Top venue rate
-0.0383%
Grvt · USDT
Detail view
KODEX200 funding
Review KODEX200 funding rates, settlement timing, and venue-by-venue snapshots from CoinCryptoRank's first-party funding feed across 9 exchanges.
9 pairs trackedscheduleexchangesverifiedFirst-party data
Venue coverage
9
Active KODEX200 snapshots
Live market snapshot
KODEX200 funding is roughly flat at +0.0070% across 9 venues — a tight +0.0433% band means no venue is paying meaningfully more, so funding arbitrage is quiet right now.
Highest
trending_up+0.0050%
Peak positive
Lowest
trending_down-0.0383%
Peak negative
Mean funding
equalizer-0.0059%
Composite
Current APY
percent-5.84%
Extrapolated from backend data.
Funding rate comparison
KODEX200 — multi-exchange funding history
Compare historical funding rates across multiple exchanges. Each exchange is a separate line.
Exchanges (select 1–6)
13 exchanges available
Stats summary
Exchanges tracked
2
Data points
0
Best spread
--
Status
Ready
Fetching funding data...
Select exchanges above to compare funding rate history.
Funding rate by venue
Current KODEX200 funding rate by exchange
Live funding rate and annualized APR for {symbol} perpetual contracts on each exchange — updated continuously from exchange data.
| Venue | Funding rate | Annualized APR | Settlement frequency | Next apply |
|---|---|---|---|---|
| BingxUSD | ▲+0.0050% | +10.95% | Every 4h | scheduleOct 16, 20:00 UTC |
| BinanceUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleOct 16, 20:00 UTC |
| BybitUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleOct 17, 00:00 UTC |
| DeepcoinUSDT | ▲0.0000% | 0.00% | Every 8h | schedule-- |
| GateUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleJan 01, 00:00 UTC |
| MexcUSDT | ▲0.0000% | 0.00% | Every 4h | scheduleOct 16, 20:00 UTC |
| XtUSDT | ▲0.0000% | 0.00% | Every 8h | schedule-- |
| BitunixUSDT | ▼-0.0197% | -21.57% | Every 8h | scheduleOct 16, 20:00 UTC |
| GrvtUSDT | ▼-0.0383% | -41.94% | Every 8h | schedule-- |
Venue breakdown
0 funding records found for KODEX200.
finance
No funding records for KODEX200 yet.
The backend snapshot may still be refreshing.