BIZTRAC BETA
Rental and operating of own or leased real estate

NOTHOLMEN DRIFT AS

Org. no. 915018297 Limited company (AS) Hustadvika Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 150,000
Operating profit NOK −115,000
Equity NOK 1.9m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−115k kr).

NOTHOLMEN DRIFT AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 915018297. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikle og drive Notholmen og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 150,000 in revenue and NOK −115,000 in operating profit.

Key figures · 2025

Revenue
NOK 150,000
Operating profit
NOK −115,000
Equity
NOK 1.9m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns NOTHOLMEN DRIFT AS?

NOTHOLMEN HOLDING AS
NOTHOLMEN DRIFT AS
NOK 150,000 rev. · NOK −115,000 profit

NOTHOLMEN DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NOTHOLMEN DRIFT AS

Who owns NOTHOLMEN DRIFT AS?

NOTHOLMEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of NOTHOLMEN DRIFT AS?

NOTHOLMEN DRIFT AS had revenue of NOK 150,000 in 2025.

Who is the general manager of NOTHOLMEN DRIFT AS?

Per Gammelsæther is registered as general manager of NOTHOLMEN DRIFT AS.

Where is NOTHOLMEN DRIFT AS based?

NOTHOLMEN DRIFT AS has its business address in Hustad.

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.