BIZTRAC BETA
Rental and operating of own or leased real estate

MIDTERHOLMEN AS

Org. no. 932694972 Limited company (AS) Nærøysund Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 40,000
Operating profit NOK −228,000
Equity NOK 3.9m
Incorporated 2023
Share capital NOK 5.2m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−228k kr).
  • Nylig endring 2026-03-27 Aksjekapital registrert 2026-03-27.

MIDTERHOLMEN AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 932694972. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 5.2m, divided into 1000 shares. The company's stated purpose is: “Å drive utleie og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 40,000 in revenue and NOK −228,000 in operating profit.

Key figures · 2024

Revenue
NOK 40,000
Operating profit
NOK −228,000
Equity
NOK 3.9m
Est. value
NOK 3.6m

Financial health · 2024

Liquidity
0.35
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.1%
Weak
Equity as a share of total capital

Who owns MIDTERHOLMEN AS?

PAULSEN & WILLIKSEN AS
MIDTERHOLMEN AS
NOK 40,000 rev. · NOK −228,000 profit

MIDTERHOLMEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIDTERHOLMEN AS

Who owns MIDTERHOLMEN AS?

PAULSEN & WILLIKSEN AS is the largest registered owner, with 100.0%.

What is the revenue of MIDTERHOLMEN AS?

MIDTERHOLMEN AS had revenue of NOK 40,000 in 2024.

Who is the general manager of MIDTERHOLMEN AS?

Sissel Margrethe Gjeset is registered as general manager of MIDTERHOLMEN AS.

Where is MIDTERHOLMEN AS based?

MIDTERHOLMEN AS has its business address in Rørvik.

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.