Top venue rate
-0.0225%
Bitget · USDT
Detail view
TWST funding
Review TWST 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 TWST snapshots
Live market snapshot
TWST funding is roughly flat at +0.0057% across 9 venues — a tight +0.0325% band means no venue is paying meaningfully more, so funding arbitrage is quiet right now.
Highest
trending_up+0.0100%
Peak positive
Lowest
trending_down-0.0225%
Peak negative
Mean funding
equalizer+0.0007%
Composite
Current APY
percent+0.82%
Extrapolated from backend data.
Funding rate comparison
TWST — 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 TWST 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 |
|---|---|---|---|---|
| BlofinUSDT | ▲+0.0100% | +10.95% | Every 8h | scheduleOct 01, 00:00 UTC |
| XtUSDT | ▲+0.0100% | +10.95% | Every 8h | schedule-- |
| BingxUSD | ▲+0.0050% | +5.48% | Every 8h | scheduleOct 17, 00:00 UTC |
| HyperliquidUSDC | ▲+0.0042% | +4.62% | Every 8h | schedule-- |
| BinanceUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleOct 17, 00:00 UTC |
| BitunixUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleOct 17, 00:00 UTC |
| BybitUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleOct 17, 00:00 UTC |
| GateUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleJan 01, 00:00 UTC |
| BitgetUSDT | ▼-0.0225% | -24.64% | Every 8h | scheduleOct 17, 00:00 UTC |
Venue breakdown
0 funding records found for TWST.
finance
No funding records for TWST yet.
The backend snapshot may still be refreshing.