BIZTRAC BETA
Construction of water projects

MIDTSTØL SJØ AS

Org. no. 997443179 Limited company (AS) Arendal Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 17.5m
Operating profit NOK −679,000
Equity NOK 5.1m
Incorporated 2011
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−679k kr).

MIDTSTØL SJØ AS is registered as a limited company in Arendal, Agder with organisation number 997443179. The business is classified under construction of water projects (NACE 42.910). The company was incorporated in 2011. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Bygg- og anleggsvirksomhet knyttet til sjønære områder herunder bygging, restaurering og vedlikehold av brygger og kaianlegg. Videre utvikling av fast eiendom samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.5m in revenue and NOK −679,000 in operating profit.

Key figures · 2024

Revenue
NOK 17.5m
Operating profit
NOK −679,000
Equity
NOK 5.1m
Est. value
NOK 6.0m

Financial health · 2024

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.3%
Good
Equity as a share of total capital

Who owns MIDTSTØL SJØ AS?

MIDTSTØL AS
MIDTSTØL SJØ AS
NOK 17.5m rev. · NOK −679,000 profit

MIDTSTØL SJØ AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MIDTSTØL SJØ AS

Who owns MIDTSTØL SJØ AS?

MIDTSTØL AS is the largest registered owner, with 50.0%.

What is the revenue of MIDTSTØL SJØ AS?

MIDTSTØL SJØ AS had revenue of NOK 17.5m in 2024.

Who is the general manager of MIDTSTØL SJØ AS?

Ruben Aanonsen is registered as general manager of MIDTSTØL SJØ AS.

Where is MIDTSTØL SJØ AS based?

MIDTSTØL SJØ AS has its business address in Saltrød.

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.