BIZTRAC BETA
Rental and operating of own or leased real estate

URDIA AS

Org. no. 925193631 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 9.0m
Operating profit NOK 4.0m
Equity NOK 60.7m
Incorporated 2020
Share capital NOK 8.2m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

URDIA AS is registered as a limited company in Oslo, Oslo with organisation number 925193631. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 8.2m, divided into 27463 shares. The company's stated purpose is: “Investering i aksjer og andre selskaper samt kjøp, salg, utvikling, utleie og drift av næringseiendommer og det som naturlig hører inn under dette, herunder deltakelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.0m in revenue and NOK 4.0m in operating profit.

Key figures · 2024

Revenue
NOK 9.0m
Operating profit
NOK 4.0m
Equity
NOK 60.7m
Est. value
NOK 54.2m

Financial health · 2024

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

Who owns URDIA AS?

CALYMENE AS
URDIA AS
NOK 9.0m rev. · NOK 4.0m profit

URDIA AS has 5 registered shareholders:

All shareholders and roles →

Which companies does URDIA AS own?

URDIA AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about URDIA AS

Who owns URDIA AS?

CALYMENE AS is the largest registered owner, with 53.5%.

What is the revenue of URDIA AS?

URDIA AS had revenue of NOK 9.0m in 2024.

Where is URDIA AS based?

URDIA 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.