BIZTRAC BETA
Site preparation

Gjøsund Maskinlag A/S

Org. no. 947590073 Limited company (AS) Giske Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 5.8m
Operating profit NOK 404,000
Equity NOK 3.4m
Incorporated 1988
Share capital NOK 250,000

Gjøsund Maskinlag A/S is registered as a limited company in Giske, Møre og Romsdal with organisation number 947590073. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1988. Registered share capital is NOK 250,000. The company's stated purpose is: “Entreprenørforretning innen maskin og anlegg, samt hva dermed står i forbindelse. Herunder eie fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.8m in revenue and NOK 404,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.8m
Operating profit
NOK 404,000
Equity
NOK 3.4m
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
3.03
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
76.9%
Very good
Equity as a share of total capital

Who owns Gjøsund Maskinlag A/S?

SVEIN GJØSUND
Gjøsund Maskinlag A/S
NOK 5.8m rev. · NOK 404,000 profit

Gjøsund Maskinlag A/S has 2 registered shareholders:

All shareholders and roles →

Which companies does Gjøsund Maskinlag A/S own?

Gjøsund Maskinlag A/S holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about Gjøsund Maskinlag A/S

Who owns Gjøsund Maskinlag A/S?

SVEIN GJØSUND is the largest registered owner, with 50.0%.

What is the revenue of Gjøsund Maskinlag A/S?

Gjøsund Maskinlag A/S had revenue of NOK 5.8m in 2025.

Who is the general manager of Gjøsund Maskinlag A/S?

Svein Gjøsund is registered as general manager of Gjøsund Maskinlag A/S.

Where is Gjøsund Maskinlag A/S based?

Gjøsund Maskinlag A/S has its business address in Valderøya.

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.