Geospace Technologies GEOS
NASDAQ GEOS
$3.44 -0.04 (-1.15%)
As of: Nov 13, 2026 · 11:01 AM EST

Geospace Technologies (GEOS) Long-Term Debt Repayments (2009 - 2013)

Updated

Geospace Technologies (GEOS) posted Long-Term Debt Repayments of $931,000 for fiscal Q1 2014 (quarter ended Dec 31, 2013).

Analysis

Geospace Technologies (GEOS) Long-Term Debt Repayments (2009 - 2013) Analysis & Trends

For FY2011 (ended Sep 30, 2011), Geospace Technologies' Long-Term Debt Repayments came in at $7.7 million, up 316.7% from FY2010.

  • In prior fiscal years, Geospace Technologies' Long-Term Debt Repayments was $1.85 million in FY2010 (+160.6%) and $709,000 in FY2009.
  • The fiscal Q1 2014 figure stands as the highest quarterly Long-Term Debt Repayments since fiscal Q1 2011.
Peer Set

Peer Comparison

# Company Market Cap Enterprise Value Gross Profit (Qtr) LT Debt Repayment (Qtr)
1 Caterpillar 276.97 Bn 248.27 Bn 7.35 Bn -30.00 Mn
2 Amphenol 188.85 Bn 183.55 Bn 4.02 Bn 937.90 Mn
3 Deere 181.51 Bn 149.60 Bn 4.66 Bn 2.40 Bn
4 Eaton 136.07 Bn 133.00 Bn 3.11 Bn 2.00 Mn
5 Parker-Hannifin 120.80 Bn 118.78 Bn 2.26 Bn 5.26 Bn
6 3M 95.85 Bn 77.30 Bn 2.78 Bn 650.00 Mn
7 Emerson Electric 92.27 Bn 84.74 Bn 2.74 Bn 2.36 Bn
8 Illinois Tool Works 81.97 Bn 78.64 Bn 1.91 Bn -
9 Vertiv Holdings 80.72 Bn 69.57 Bn 1.64 Bn 15.30 Mn
10 Geospace Technologies 44.75 Mn -8.35 Mn 496,000.00 -
Historic Data

Historic Data

Download Data
DateValue
Dec 31, 2013 931,000.00
Dec 31, 2010 7.70 Mn
Sep 30, 2010 110,000.00
Jun 30, 2010 3.37 Mn
Mar 31, 2010 -110,000.00
Dec 31, 2009 -1.52 Mn
Sep 30, 2009 1.24 Mn
Jun 30, 2009 -178,000.00
Mar 31, 2009 -177,000.00
API Access

Geospace Technologies Long-Term Debt Repayments 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=long-term-debt-repayments&ticker=GEOS&period=max&api_key=YOUR_API_KEY