BIZTRAC BETA
Other real estate activities on a fee or contract basis

BOVG EIENDOM AS

Org. no. 935870984 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −21,000
Equity NOK 5.0m
Incorporated 2025
Share capital NOK 5.2m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).
  • Nylig endring 2026-02-24 Aksjekapital registrert 2026-02-24.

BOVG EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 935870984. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2025. Registered share capital is NOK 5.2m, divided into 10500 shares. The company's stated purpose is: “Leie og forvalte fast eiendom, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −21,000
Equity
NOK 5.0m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns BOVG EIENDOM AS?

BYGGMESTER ESPEGARD AS
BOVG EIENDOM AS
NOK 0 rev. · NOK −21,000 profit

BOVG EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Which companies does BOVG EIENDOM AS own?

BOVG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BOVG EIENDOM AS

Who owns BOVG EIENDOM AS?

BYGGMESTER ESPEGARD AS is the largest registered owner, with 20.0%.

What is the revenue of BOVG EIENDOM AS?

BOVG EIENDOM AS had revenue of NOK 0 in 2025.

Where is BOVG EIENDOM AS based?

BOVG EIENDOM AS has its business address in Drammen.

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.