BIZTRAC BETA
Development of building projects

BRUNLANES NÆRING AS

Org. no. 923377670 Limited company (AS) Larvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 20,000
Operating profit NOK −92,000
Equity NOK 7.5m
Incorporated 2019
Share capital NOK 100,000

Signals

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

BRUNLANES NÆRING AS is registered as a limited company in Larvik, Vestfold with organisation number 923377670. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og andre eierandeler i selskaper og foretak, samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 20,000 in revenue and NOK −92,000 in operating profit.

Key figures · 2024

Revenue
NOK 20,000
Operating profit
NOK −92,000
Equity
NOK 7.5m
Est. value
NOK 36.2m

Financial health · 2024

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

Who owns BRUNLANES NÆRING AS?

HORTULAN JV AS
BRUNLANES NÆRING AS
NOK 20,000 rev. · NOK −92,000 profit

BRUNLANES NÆRING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BRUNLANES NÆRING AS own?

BRUNLANES NÆRING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BRUNLANES NÆRING AS

Who owns BRUNLANES NÆRING AS?

HORTULAN JV AS is the largest registered owner, with 45.9%.

What is the revenue of BRUNLANES NÆRING AS?

BRUNLANES NÆRING AS had revenue of NOK 20,000 in 2024.

Where is BRUNLANES NÆRING AS based?

BRUNLANES NÆRING AS has its business address in Larvik.

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.