BIZTRAC BETA
Rental and operating of own or leased real estate

URANIENBORG AS

Org. no. 987888369 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 728,000
Operating profit NOK 63,000
Equity NOK 3.7m
Incorporated 2005
Share capital NOK 100,000

URANIENBORG AS is registered as a limited company in Oslo, Oslo with organisation number 987888369. 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 100 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper, annen tilsvarende plassering og forvaltning av egne midler, investering og utvikling fast eiendom, konsulentbistand innen internkontrollarbeid og det som hører naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 728,000 in revenue and NOK 63,000 in operating profit.

Key figures · 2025

Revenue
NOK 728,000
Operating profit
NOK 63,000
Equity
NOK 3.7m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns URANIENBORG AS?

STEIN ERIK DÜRING
URANIENBORG AS
NOK 728,000 rev. · NOK 63,000 profit

URANIENBORG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does URANIENBORG AS own?

URANIENBORG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about URANIENBORG AS

Who owns URANIENBORG AS?

STEIN ERIK DÜRING is the largest registered owner, with 100.0%.

What is the revenue of URANIENBORG AS?

URANIENBORG AS had revenue of NOK 728,000 in 2025.

Where is URANIENBORG AS based?

URANIENBORG AS has its business address in Oslo.

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.