biztrac. BETA
COMPANY REGISTER PROFILE
932272717 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

UNION EIENDOM 20 AS

Org. no. 932272717 Limited company (AS) Oslo Incorporated 2023 Active
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 24,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

UNION EIENDOM 20 AS is registered as a limited company in Oslo, Oslo with organisation number 932272717. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i fast eiendom eller aksjer i selskaper som eier fast eiendom, utvikle, omsette, leie ut og for øvrig administrere fast eiendom, og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
▲ +0 %
Equity
NOK 24,000
▼ −1 %
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns UNION EIENDOM 20 AS?

UNION EIENDOM 20 AS
NOK 0 rev. · NOK −1,000 profit

UNION EIENDOM 20 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UNION EIENDOM 20 AS

Who owns UNION EIENDOM 20 AS?

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

What is the revenue of UNION EIENDOM 20 AS?

UNION EIENDOM 20 AS had revenue of NOK 0 in 2025.

Where is UNION EIENDOM 20 AS based?

UNION EIENDOM 20 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.