BIZTRAC BETA
Other real estate activities on a fee or contract basis

UNION DRIFT UREF III AS

Org. no. 821893062 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 8.6m
Operating profit NOK −33,000
Equity NOK 368,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

UNION DRIFT UREF III AS is registered as a limited company in Oslo, Oslo with organisation number 821893062. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie fast eiendom eller aksjer i selskaper som eier fast eiendom, utvikle, omsette, leie ut og for øvrig administrere fast eiendom, samt hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.6m in revenue and NOK −33,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.6m
Operating profit
NOK −33,000
Equity
NOK 368,000
Est. value
NOK 6.8m

Financial health · 2025

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

Who owns UNION DRIFT UREF III AS?

UNION MANAGEMENT AS
UNION DRIFT UREF III AS
NOK 8.6m rev. · NOK −33,000 profit

UNION DRIFT UREF III AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UNION DRIFT UREF III AS

Who owns UNION DRIFT UREF III AS?

UNION MANAGEMENT AS is the largest registered owner, with 100.0%.

What is the revenue of UNION DRIFT UREF III AS?

UNION DRIFT UREF III AS had revenue of NOK 8.6m in 2025.

Where is UNION DRIFT UREF III AS based?

UNION DRIFT UREF III 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.