Radcom (RDCM) Interest Coverage Ratio (2009 - 2025)
Radcom's Interest Coverage Ratio came in at 243.67 for the quarter ended Mar 31, 2025, compared with -8.38 a year earlier.
Powered by 
Analysis
Radcom (RDCM) Interest Coverage Ratio (2009 - 2025) Analysis & Trends
Over the trailing twelve months to Mar 31, 2025, Radcom reported Interest Coverage Ratio of 21.60; for the year ended Dec 31, 2009, it was -5.02.
- The figure for the quarter ended Mar 31, 2025 represents the highest quarterly Interest Coverage Ratio since the quarter ended Mar 31, 2010.
Peer Set
Peer Comparison
| # | Company | Market Cap | Enterprise Value | Gross Profit (Qtr) | Interest Cover (Qtr) |
|---|---|---|---|---|---|
| 1 | Palo Alto Networks | 255.42 Bn | 240.49 Bn | 2.30 Bn | - |
| 2 | CrowdStrike Holdings | 232.07 Bn | 212.47 Bn | 1.10 Bn | -5.50 |
| 3 | Fortinet | 125.35 Bn | 111.28 Bn | 1.64 Bn | 215.41 |
| 4 | Snowflake | 111.63 Bn | 98.94 Bn | 1.04 Bn | -126.37 |
| 5 | Datadog | 91.35 Bn | 72.99 Bn | 881.34 Mn | 1.68 |
| 6 | Zscaler | 34.43 Bn | 20.55 Bn | - | - |
| 7 | Okta | 33.87 Bn | 23.97 Bn | 641.00 Mn | 5.63 |
| 8 | Axon Enterprise | 31.65 Bn | 26.18 Bn | 546.45 Mn | 1.66 |
| 9 | MongoDB | 29.46 Bn | 19.93 Bn | 569.77 Mn | 30.74 |
| 10 | Radcom | 165.92 Mn | -268.82 Mn | - | - |
Historic Data
Download Data
Historic Data
| Date | Value |
|---|---|
| Mar 31, 2025 | 243.67 |
| Mar 31, 2024 | -8.38 |
| Mar 31, 2016 | 2.15 |
| Mar 31, 2015 | 1.98 |
| Dec 31, 2014 | 0.28 |
| Sep 30, 2014 | 3.51 |
| Dec 31, 2013 | 0.70 |
| Sep 30, 2013 | -12.51 |
| Jun 30, 2013 | 9.87 |
| Mar 31, 2013 | -5,123.71 |
| Dec 31, 2012 | -0.64 |
| Sep 30, 2012 | -257.57 |
| Jun 30, 2012 | -16.41 |
| Mar 31, 2012 | -25,583.33 |
| Dec 31, 2011 | 0.94 |
| Dec 31, 2010 | 0.05 |
| Mar 31, 2010 | 1,149.56 |
| Dec 31, 2009 | 1.36 |
| Mar 31, 2009 | -9.96 |
API Access
Radcom Interest Coverage Ratio API
Pull this series into your own models, spreadsheets and apps with the Business Quant
Historical Metrics API. The request below matches the chart above — change the
frequency, period or values and it follows. Swap YOUR_API_KEY for your own key.
https://data.businessquant.com/historic?slug=interest-coverage-ratio&ticker=RDCM&period=max&api_key=YOUR_API_KEYimport requests
url = "https://data.businessquant.com/historic"
params = {"slug": "interest-coverage-ratio", "ticker": "RDCM", "period": "max", "api_key": "YOUR_API_KEY"}
data = requests.get(url, params=params).json()const res = await fetch("https://data.businessquant.com/historic?slug=interest-coverage-ratio&ticker=RDCM&period=max&api_key=YOUR_API_KEY");
const data = await res.json();