Iveda Solutions (IVDA) Total Non-Current Liabilities (2012 - 2015)
Iveda Solutions (IVDA) reported Total Non-Current Liabilities of $4.03 million for Q4 2015, down 2.5% from $4.13 million a year earlier.
Powered by 
Analysis
Iveda Solutions (IVDA) Total Non-Current Liabilities (2012 - 2015) Analysis & Trends
Dating back to Q4 2012, Iveda Solutions' Total Non-Current Liabilities record includes 7 quarters.
- Total Non-Current Liabilities has a three-year compound annual growth rate of 2.5% (FY2012 to FY2015).
- By year, Total Non-Current Liabilities came in at $4.13 million in FY2014 (+33.7%), $3.09 million in FY2013 (-17.4%) and $3.74 million in FY2012.
- The Q4 2015 figure ranks as the lowest quarterly Total Non-Current Liabilities since Q4 2013.
Peer Set
Peer Comparison
| # | Company | Market Cap | Enterprise Value | Gross Profit (Qtr) | Total Non-Current Liabilities (Qtr) |
|---|---|---|---|---|---|
| 1 | Palo Alto Networks | 323.81 Bn | 308.88 Bn | 2.30 Bn | 19.68 Bn |
| 2 | CrowdStrike Holdings | 271.09 Bn | 251.53 Bn | 1.10 Bn | 6.57 Bn |
| 3 | Fortinet | 131.14 Bn | 117.07 Bn | 1.64 Bn | 9.17 Bn |
| 4 | Snowflake | 119.71 Bn | 107.03 Bn | 1.04 Bn | 6.45 Bn |
| 5 | Datadog | 98.30 Bn | 79.94 Bn | 881.34 Mn | 3.16 Bn |
| 6 | Okta | 34.95 Bn | 25.05 Bn | 641.00 Mn | 2.11 Bn |
| 7 | Axon Enterprise | 34.32 Bn | 28.85 Bn | 546.45 Mn | 3.68 Bn |
| 8 | Zscaler | 32.52 Bn | 18.64 Bn | - | 5.20 Bn |
| 9 | Baidu | 29.56 Bn | -44.07 Bn | 1.47 Mn | 12.63 Bn |
| 10 | Iveda Solutions | 3.76 Mn | -15.32 Mn | 438,562.00 | - |
Historic Data
Download Data
Historic Data
| Date | Value |
|---|---|
| Dec 31, 2015 | 4.03 Mn |
| Dec 31, 2014 | 4.13 Mn |
| Sep 30, 2014 | 7.11 Mn |
| Jun 30, 2014 | 6.20 Mn |
| Mar 31, 2014 | 4.95 Mn |
| Dec 31, 2013 | 3.09 Mn |
| Dec 31, 2012 | 3.74 Mn |
API Access
Iveda Solutions Total Non-Current Liabilities 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=total-non-current-liabilities&ticker=IVDA&period=max&api_key=YOUR_API_KEYimport requests
url = "https://data.businessquant.com/historic"
params = {"slug": "total-non-current-liabilities", "ticker": "IVDA", "period": "max", "api_key": "YOUR_API_KEY"}
data = requests.get(url, params=params).json()const res = await fetch("https://data.businessquant.com/historic?slug=total-non-current-liabilities&ticker=IVDA&period=max&api_key=YOUR_API_KEY");
const data = await res.json();