BIZTRAC BETA
Sports activities n.e.c.

GSAT HOLDING AS

Org. no. 933897885 Limited company (AS) Namsos Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 676,000
Operating profit NOK 278,000
Equity NOK 56,000
Incorporated 2024
Share capital NOK 30,000

GSAT HOLDING AS is registered as a limited company in Namsos, Trøndelag with organisation number 933897885. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementære til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”. The most recent filed accounts, for the 2025 financial year, show NOK 676,000 in revenue and NOK 278,000 in operating profit.

Key figures · 2025

Revenue
NOK 676,000
Operating profit
NOK 278,000
Equity
NOK 56,000
Est. value
NOK 791,000

Financial health · 2025

Liquidity
1.87
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GSAT HOLDING AS?

GEIR HÅVARD SÆTHER
GSAT HOLDING AS
NOK 676,000 rev. · NOK 278,000 profit

GSAT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GSAT HOLDING AS own?

GSAT HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GSAT HOLDING AS

Who owns GSAT HOLDING AS?

GEIR HÅVARD SÆTHER is the largest registered owner, with 100.0%.

What is the revenue of GSAT HOLDING AS?

GSAT HOLDING AS had revenue of NOK 676,000 in 2025.

Where is GSAT HOLDING AS based?

GSAT HOLDING AS has its business address in Spillum.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.