BIZTRAC BETA
Intermediation service activities for real estate activities

BELEVEN EIENDOM AS

Org. no. 929627733 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 191,000
Equity NOK 310,000
Incorporated 2022
Share capital NOK 35,000

Signals

1 flags
  • Nylig endring 2026-06-03 Adresseendring registrert 2026-06-03.

BELEVEN EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 929627733. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2022. Registered share capital is NOK 35,000, divided into 353 shares. The company's stated purpose is: “Drive franchisevirksomhet innenfor eiendomsmeglingsvirksomhet og dertil knyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 191,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 191,000
Equity
NOK 310,000
Est. value
NOK 717,000

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.3%
Weak
Equity as a share of total capital

Who owns BELEVEN EIENDOM AS?

DSM HOLDING AS
BELEVEN EIENDOM AS
NOK 1.7m rev. · NOK 191,000 profit

BELEVEN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BELEVEN EIENDOM AS own?

BELEVEN EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BELEVEN EIENDOM AS

Who owns BELEVEN EIENDOM AS?

DSM HOLDING AS is the largest registered owner, with 39.9%.

What is the revenue of BELEVEN EIENDOM AS?

BELEVEN EIENDOM AS had revenue of NOK 1.7m in 2025.

Where is BELEVEN EIENDOM AS based?

BELEVEN EIENDOM AS has its business address in Oslo.

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.