BIZTRAC BETA
Rental and operating of own or leased real estate

JENSEN EIENDOMSUTVIKLING AS

Org. no. 989159356 Limited company (AS) Ringerike Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 2.5m
Equity NOK 16.7m
Incorporated 2005
Share capital NOK 100,000

JENSEN EIENDOMSUTVIKLING AS is registered as a limited company in Ringerike, Buskerud with organisation number 989159356. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utleie av fast eiendom. Utleie samt kjøp og salg av leiligheter og eneboliger. ”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 2.5m in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 2.5m
Equity
NOK 16.7m
Est. value
NOK 18.0m

Financial health · 2025

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
84.3%
Very good
Equity as a share of total capital

Who owns JENSEN EIENDOMSUTVIKLING AS?

MORTEN JENSEN
JENSEN EIENDOMSUTVIKLING AS
NOK 4.0m rev. · NOK 2.5m profit

JENSEN EIENDOMSUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JENSEN EIENDOMSUTVIKLING AS

Who owns JENSEN EIENDOMSUTVIKLING AS?

MORTEN JENSEN is the largest registered owner, with 100.0%.

What is the revenue of JENSEN EIENDOMSUTVIKLING AS?

JENSEN EIENDOMSUTVIKLING AS had revenue of NOK 4.0m in 2025.

Who is the general manager of JENSEN EIENDOMSUTVIKLING AS?

Morten Jensen is registered as general manager of JENSEN EIENDOMSUTVIKLING AS.

Where is JENSEN EIENDOMSUTVIKLING AS based?

JENSEN EIENDOMSUTVIKLING AS has its business address in Hønefoss.

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.