BIZTRAC BETA
Rental and operating of own or leased real estate

HORTEN BOLIG AS

Org. no. 921336845 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 13,000
Operating profit NOK −211,000
Equity NOK 43.8m
Incorporated 2018
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−211k kr).

HORTEN BOLIG AS is registered as a limited company in Drammen, Buskerud with organisation number 921336845. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Ervervelse, drift og utvikling av fast eiendom og hva dermed står i forbindelse, samt videre deltagelse i andre selskaper ved aksjetegning og på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 13,000 in revenue and NOK −211,000 in operating profit.

Key figures · 2025

Revenue
NOK 13,000
Operating profit
NOK −211,000
Equity
NOK 43.8m
Est. value
NOK 188.4m

Financial health · 2025

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.0%
Satisfactory
Equity as a share of total capital

Who owns HORTEN BOLIG AS?

MARIENLYST EIENDOM AS
HORTEN BOLIG AS
NOK 13,000 rev. · NOK −211,000 profit

HORTEN BOLIG AS has 2 registered shareholders:

All shareholders and roles →

Group structure

HORTEN BOLIG AS er morselskap for 9 datterselskaper:

Frequently asked questions about HORTEN BOLIG AS

Who owns HORTEN BOLIG AS?

MARIENLYST EIENDOM AS is the largest registered owner, with 90.0%.

What is the revenue of HORTEN BOLIG AS?

HORTEN BOLIG AS had revenue of NOK 13,000 in 2025.

Where is HORTEN BOLIG AS based?

HORTEN BOLIG 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.