BIZTRAC BETA
Buying and selling of own real estate

BM EIENDOM AS

Org. no. 919530006 Limited company (AS) Bergen Incorporated 1970 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 2.4m
Equity NOK 3.7m
Incorporated 1970
Share capital NOK 495,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BM EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 919530006. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1970. Registered share capital is NOK 495,000, divided into 1500 shares. The company's stated purpose is: “Kjøp, salg og utleie av egen fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 2.4m
Equity
NOK 3.7m
Est. value
NOK 8.1m

Financial health · 2024

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

Who owns BM EIENDOM AS?

NESTTUN INVEST EIENDOM AS
BM EIENDOM AS
NOK 4.3m rev. · NOK 2.4m profit

BM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BM EIENDOM AS er morselskap for 8 datterselskaper:

Frequently asked questions about BM EIENDOM AS

Who owns BM EIENDOM AS?

NESTTUN INVEST EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BM EIENDOM AS?

BM EIENDOM AS had revenue of NOK 4.3m in 2024.

Who is the general manager of BM EIENDOM AS?

Pål Brynjulfsen Kvalheim is registered as general manager of BM EIENDOM AS.

Where is BM EIENDOM AS based?

BM EIENDOM AS has its business address in Paradis.

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.