Gitlab (GTLB) Depreciation and Depletion (2022 - 2024)
Gitlab (GTLB) recorded Depreciation and Depletion of $3.3 million in FY2026 (year ended Jan 31, 2026), up 13.8% from $2.9 million in FY2025.
Analysis
Gitlab (GTLB) Depreciation and Depletion (2022 - 2024) Analysis & Trends
Starting with FY2022, Gitlab's Depreciation and Depletion history includes 5 fiscal years.
- Annual Depreciation and Depletion has a four-year compound annual growth rate of 60.3% (FY2022 to FY2026).
- Annual Depreciation and Depletion has ranged from $500,000 in FY2022 to $4.4 million in FY2024 over the past five years.
- Per Business Quant data, GTLB's Depreciation and Depletion was $2.9 million in FY2025 (-34.1%), $4.4 million in FY2024 (+37.5%), $3.2 million in FY2023 (+540.0%) and $500,000 in FY2022.
Peer Set
Peer Comparison
| # | Company | Market Cap | Enterprise Value | Gross Profit (Qtr) | Dep. & Depletion (Qtr) |
|---|---|---|---|---|---|
| 1 | Palo Alto Networks | 328.64 Bn | 313.71 Bn | 2.30 Bn | - |
| 2 | CrowdStrike Holdings | 276.50 Bn | 256.94 Bn | 1.10 Bn | - |
| 3 | Fortinet | 132.74 Bn | 118.67 Bn | 1.64 Bn | 31.50 Mn |
| 4 | Snowflake | 120.19 Bn | 107.50 Bn | 1.04 Bn | 26.40 Mn |
| 5 | Datadog | 99.51 Bn | 81.15 Bn | 881.34 Mn | - |
| 6 | Okta | 35.35 Bn | 25.44 Bn | 641.00 Mn | - |
| 7 | Axon Enterprise | 33.58 Bn | 28.10 Bn | 546.45 Mn | - |
| 8 | Zscaler | 32.06 Bn | 18.18 Bn | - | - |
| 9 | MongoDB | 28.84 Bn | 19.30 Bn | 569.77 Mn | 993,000.00 |
| 10 | Gitlab | 8.27 Bn | 3.24 Bn | 240.62 Mn | - |
Historic Data
Download Data
Historic Data
| Date | Value |
|---|---|
| Jan 31, 2024 | 1.10 Mn |
| Oct 31, 2023 | 1.10 Mn |
| Jul 31, 2023 | 1.10 Mn |
| Apr 30, 2023 | 1.10 Mn |
| Jan 31, 2023 | 1.00 Mn |
| Oct 31, 2022 | 900,000.00 |
| Jul 31, 2022 | 700,000.00 |
| Apr 30, 2022 | 600,000.00 |
| Jan 31, 2022 | 500,000.00 |
API Access
Gitlab Depreciation and Depletion 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=depreciation-and-depletion&ticker=GTLB&period=max&api_key=YOUR_API_KEY
import requests
url = "https://data.businessquant.com/historic"
params = {"slug": "depreciation-and-depletion", "ticker": "GTLB", "period": "max", "api_key": "YOUR_API_KEY"}
data = requests.get(url, params=params).json()
const res = await fetch("https://data.businessquant.com/historic?slug=depreciation-and-depletion&ticker=GTLB&period=max&api_key=YOUR_API_KEY");
const data = await res.json();