BIZTRAC BETA
Development of building projects

URANIENBORG UTBYGGINGSSELSKAB AS

Org. no. 915542093 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 412,000
Equity NOK −3.7m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,7 mill kr).

URANIENBORG UTBYGGINGSSELSKAB AS is registered as a limited company in Bærum, Akershus with organisation number 915542093. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i og utvikling av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 412,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 412,000
Equity
NOK −3.7m
Est. value
NOK 4.4m

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns URANIENBORG UTBYGGINGSSELSKAB AS?

MERCER INVEST AS
URANIENBORG UTBYGGINGSSELSKAB AS
NOK 0 rev. · NOK 412,000 profit

URANIENBORG UTBYGGINGSSELSKAB AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about URANIENBORG UTBYGGINGSSELSKAB AS

Who owns URANIENBORG UTBYGGINGSSELSKAB AS?

MERCER INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of URANIENBORG UTBYGGINGSSELSKAB AS?

URANIENBORG UTBYGGINGSSELSKAB AS had revenue of NOK 0 in 2024.

Where is URANIENBORG UTBYGGINGSSELSKAB AS based?

URANIENBORG UTBYGGINGSSELSKAB AS has its business address in Snarøya.

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.