Netskope (NTSK) Change in Receivables (2025 - 2026)
Netskope (NTSK) recorded Change in Receivables of $51.84 million in fiscal Q2 2027 (quarter ended Jul 31, 2026), up 62.7% from $31.86 million a year earlier.
Netskope (NTSK) Change in Receivables (2025 - 2026) Analysis & Trends
On a TTM basis, Netskope's Change in Receivables came in at $40.66 million as of Jul 31, 2026; for FY2026 (ended Jan 31, 2026), it came in at -$36.82 million.
- Across earlier fiscal years, Change in Receivables came in at $81.13 million in FY2025 (+890.3%) and $8.19 million in FY2024.
- The fiscal Q2 2027 figure is the highest quarterly Change in Receivables since fiscal Q4 2025.
- Per Business Quant, the preceding three fiscal quarters came in at -$22.15 million (Q1 2027), $26.74 million (Q4 2026) and -$15.77 million (Q3 2026).
Peer Comparison
| # | Company | Market Cap | Enterprise Value | Gross Profit (Qtr) | Change Receivables (Qtr) |
|---|---|---|---|---|---|
| 1 | Palo Alto Networks | 319.55 Bn | 304.63 Bn | 2.30 Bn | 776.00 Mn |
| 2 | CrowdStrike Holdings | 265.46 Bn | 245.90 Bn | 1.10 Bn | 104.65 Mn |
| 3 | Fortinet | 129.36 Bn | 115.29 Bn | 1.64 Bn | -29.90 Mn |
| 4 | Snowflake | 115.65 Bn | 102.97 Bn | 1.04 Bn | 146.59 Mn |
| 5 | Datadog | 96.45 Bn | 78.09 Bn | 881.34 Mn | 151.65 Mn |
| 6 | Axon Enterprise | 34.50 Bn | 29.03 Bn | 546.45 Mn | 305.83 Mn |
| 7 | Okta | 33.79 Bn | 23.89 Bn | 641.00 Mn | 83.00 Mn |
| 8 | Zscaler | 32.51 Bn | 18.63 Bn | - | - |
| 9 | Baidu | 29.59 Bn | -44.04 Bn | 1.47 Mn | - |
| 10 | Netskope | 7.28 Bn | 2.80 Bn | 163.02 Mn | 51.84 Mn |
Historic Data
| Date | Value |
|---|---|
| Jul 31, 2026 | 51.84 Mn |
| Apr 30, 2026 | -22.15 Mn |
| Jan 31, 2026 | 26.74 Mn |
| Oct 31, 2025 | -15.77 Mn |
| Jul 31, 2025 | 31.86 Mn |
| Apr 30, 2025 | -79.66 Mn |
| Jan 31, 2025 | 68.65 Mn |
Netskope Change in Receivables 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=change-in-receivables&ticker=NTSK&period=max&api_key=YOUR_API_KEY
import requests
url = "https://data.businessquant.com/historic"
params = {"slug": "change-in-receivables", "ticker": "NTSK", "period": "max", "api_key": "YOUR_API_KEY"}
data = requests.get(url, params=params).json()
const res = await fetch("https://data.businessquant.com/historic?slug=change-in-receivables&ticker=NTSK&period=max&api_key=YOUR_API_KEY");
const data = await res.json();