biztrac. BETA
COMPANY REGISTER PROFILE
923584811 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

BRØDRENE NÆSS INVEST AS

Org. no. 923584811 Limited company (AS) Holmestrand Incorporated 2019 Active
Operating profit NOK −23,000
Equity NOK 24,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

BRØDRENE NÆSS INVEST AS is registered as a limited company in Holmestrand, Vestfold with organisation number 923584811. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å investere i aksjer, andeler i selskap etter selskapsloven, utenlandske selskaper, obligasjoner, fast eiendom og annet som står naturlig i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −23,000
▲ +4 %
Equity
NOK 24,000
▼ −49 %
Est. value
NOK 25,000

Financial health · 2025

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
-1.6%
Not satisfactory
Return on total assets
Solidity
1.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BRØDRENE NÆSS INVEST AS?

BRØDRENE NÆSS INVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BRØDRENE NÆSS INVEST AS own?

BRØDRENE NÆSS INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BRØDRENE NÆSS INVEST AS

Who owns BRØDRENE NÆSS INVEST AS?

Fredrik Hempel Næss is the largest registered owner, with 75.0%.

Where is BRØDRENE NÆSS INVEST AS based?

BRØDRENE NÆSS INVEST AS has its business address in Sande I Vestfold.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.