BIZTRAC BETA
COMPANY REGISTER PROFILE
997649710 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

BARO INDUSTRIEIENDOM AS

Org. no. 997649710 Limited company (AS) Herøy Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 2.0m
Equity NOK 16.5m
Incorporated 2011
Share capital NOK 100,000

BARO INDUSTRIEIENDOM AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 997649710. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Investering i og utleie av fast eiendom og det som naturlig hører til dette, samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 2.0m
Equity
NOK 16.5m
Est. value
NOK 14.8m

Financial health · 2025

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

Who owns BARO INDUSTRIEIENDOM AS?

BARO INDUSTRIEIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BARO INDUSTRIEIENDOM AS

Who owns BARO INDUSTRIEIENDOM AS?

ULMATEC EIENDOM AS is the largest registered owner, with 70.0%.

What is the revenue of BARO INDUSTRIEIENDOM AS?

BARO INDUSTRIEIENDOM AS had revenue of NOK 3.9m in 2025.

Who is the general manager of BARO INDUSTRIEIENDOM AS?

Stig Kolbein Ulstein is registered as general manager of BARO INDUSTRIEIENDOM AS.

Where is BARO INDUSTRIEIENDOM AS based?

BARO INDUSTRIEIENDOM AS has its business address in Fosnavåg.

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

Report a problem

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