BIZTRAC BETA
Development of building projects

PARADIS BOLIGUTVIKLING 1 AS

Org. no. 915855415 Limited company (AS) Stavanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 236.0m
Operating profit NOK −4.4m
Equity NOK 62.3m
Incorporated 2015
Share capital NOK 1.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,4 mill kr).

PARADIS BOLIGUTVIKLING 1 AS is registered as a limited company in Stavanger, Rogaland with organisation number 915855415. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 1.5m, divided into 1500 shares. The company's stated purpose is: “Erverve, utvikle, oppføre og selge fast eiendom og alt som herved står i forbindelse med dette. Samt investere i andre selskaper med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 236.0m in revenue and NOK −4.4m in operating profit.

Key figures · 2024

Revenue
NOK 236.0m
Operating profit
NOK −4.4m
Equity
NOK 62.3m
Est. value
NOK 225.0m

Financial health · 2024

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

Who owns PARADIS BOLIGUTVIKLING 1 AS?

BANE NOR EIENDOM AS
PARADIS BOLIGUTVIKLING 1 AS
NOK 236.0m rev. · NOK −4.4m profit

PARADIS BOLIGUTVIKLING 1 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PARADIS BOLIGUTVIKLING 1 AS

Who owns PARADIS BOLIGUTVIKLING 1 AS?

BANE NOR EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of PARADIS BOLIGUTVIKLING 1 AS?

PARADIS BOLIGUTVIKLING 1 AS had revenue of NOK 236.0m in 2024.

Where is PARADIS BOLIGUTVIKLING 1 AS based?

PARADIS BOLIGUTVIKLING 1 AS has its business address in Stavanger.

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.