BIZTRAC BETA
Rental and operating of own or leased real estate

BREIMYR EIENDOM AS

Org. no. 915450385 Limited company (AS) Froland Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 438,000
Operating profit NOK −8,000
Equity NOK 2.5m
Incorporated 2015
Share capital NOK 30,000

Signals

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

BREIMYR EIENDOM AS is registered as a limited company in Froland, Agder with organisation number 915450385. 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: “Investering i andre selskaper, investering i fast eiendom og annet som herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 438,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 438,000
Operating profit
NOK −8,000
Equity
NOK 2.5m
Est. value
NOK 3.1m

Financial health · 2024

Liquidity
0.84
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.4%
Good
Equity as a share of total capital

Who owns BREIMYR EIENDOM AS?

KNUT OLAV BREIMYR
BREIMYR EIENDOM AS
NOK 438,000 rev. · NOK −8,000 profit

BREIMYR EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BREIMYR EIENDOM AS own?

BREIMYR EIENDOM AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about BREIMYR EIENDOM AS

Who owns BREIMYR EIENDOM AS?

KNUT OLAV BREIMYR is the largest registered owner, with 100.0%.

What is the revenue of BREIMYR EIENDOM AS?

BREIMYR EIENDOM AS had revenue of NOK 438,000 in 2024.

Where is BREIMYR EIENDOM AS based?

BREIMYR EIENDOM AS has its business address in Froland.

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.