BIZTRAC BETA
Construction of residential and non-residential buildings

HERLOF FLOSAND INVEST AS

Org. no. 930236934 Limited company (AS) Nærøysund Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −27,000
Equity NOK 28.6m
Incorporated 2022
Share capital NOK 91,000

Signals

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

HERLOF FLOSAND INVEST AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 930236934. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 91,000, divided into 6500 shares. The company's stated purpose is: “Selskapets virksomhet er selv, eller gjennom hel- eller deleide selskaper, eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, fast eiendom, samt annen virksomhet som har naturlig sammenheng med dette.”.

Key figures · 2024

Operating profit
NOK −27,000
Equity
NOK 28.6m
Est. value
NOK 29.4m

Financial health · 2024

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

Who owns HERLOF FLOSAND INVEST AS?

HERLOF RONI FLOSAND
HERLOF FLOSAND INVEST AS
· NOK −27,000 profit

HERLOF FLOSAND INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HERLOF FLOSAND INVEST AS own?

HERLOF FLOSAND INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HERLOF FLOSAND INVEST AS

Who owns HERLOF FLOSAND INVEST AS?

HERLOF RONI FLOSAND is the largest registered owner, with 100.0%.

Where is HERLOF FLOSAND INVEST AS based?

HERLOF FLOSAND INVEST 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.