Twilio (TWLO) Non-Current Deferred Tax Liability (2017 - 2018)
Twilio's Non-Current Deferred Tax Liability was $5.18 million in Q4 2018, up 111.3% from $2.45 million a year earlier and up 6.8% from the prior quarter.
Analysis
Twilio (TWLO) Non-Current Deferred Tax Liability (2017 - 2018) Analysis & Trends
From Q1 2017 onward, Twilio has reported Non-Current Deferred Tax Liability for 8 quarters.
- In earlier years, Non-Current Deferred Tax Liability was $2.45 million in FY2017.
- The Q4 2018 figure marks the highest quarterly Non-Current Deferred Tax Liability in data going back to Q1 2017.
- Compared with a year earlier, Non-Current Deferred Tax Liability was higher in two of the last four quarters, with growth averaging 36.3%.
- Per Business Quant data, TWLO's Non-Current Deferred Tax Liability in the three quarters before Q4 2018 was $4.85 million (Q3 2018), $1.89 million (Q2 2018) and $2.26 million (Q1 2018).
Peer Set
Peer Comparison
| # | Company | Market Cap | Enterprise Value | Gross Profit (Qtr) |
|---|---|---|---|---|
| 1 | Adobe | 93.82 Bn | 69.07 Bn | 6.00 Bn |
| 2 | Atlassian | 46.64 Bn | 39.92 Bn | 1.53 Bn |
| 3 | Twilio | 44.91 Bn | 34.90 Bn | 725.87 Mn |
| 4 | Autodesk | 43.68 Bn | 31.72 Bn | 1.87 Bn |
| 5 | Zoom Communications | 26.53 Bn | -4.25 Bn | 985.50 Mn |
| 6 | Figma | 11.16 Bn | 4.66 Bn | 309.61 Mn |
| 7 | Dropbox | 7.44 Bn | 3.07 Bn | 506.50 Mn |
| 8 | Nice | 6.72 Bn | 5.19 Bn | 995.81 Mn |
| 9 | RingCentral | 6.26 Bn | 5.75 Bn | 472.31 Mn |
| 10 | Open Text | 5.43 Bn | 861.81 Mn | 1.01 Bn |
Historic Data
Download Data
Historic Data
| Date | Value |
|---|---|
| Dec 31, 2018 | 5.18 Mn |
| Sep 30, 2018 | 4.85 Mn |
| Jun 30, 2018 | 1.89 Mn |
| Mar 31, 2018 | 2.26 Mn |
| Dec 31, 2017 | 2.45 Mn |
| Sep 30, 2017 | 2.78 Mn |
| Jun 30, 2017 | 2.68 Mn |
| Mar 31, 2017 | 2.54 Mn |
API Access
Twilio Non-Current Deferred Tax Liability 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=non-current-deferred-tax-liability&ticker=TWLO&period=max&api_key=YOUR_API_KEY
import requests
url = "https://data.businessquant.com/historic"
params = {"slug": "non-current-deferred-tax-liability", "ticker": "TWLO", "period": "max", "api_key": "YOUR_API_KEY"}
data = requests.get(url, params=params).json()
const res = await fetch("https://data.businessquant.com/historic?slug=non-current-deferred-tax-liability&ticker=TWLO&period=max&api_key=YOUR_API_KEY");
const data = await res.json();