BIZTRAC BETA
Rental and operating of own or leased real estate

URALUR EIENDOM AS

Org. no. 932487055 Limited company (AS) Sirdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 222,000
Operating profit NOK −1.1m
Equity NOK −2.0m
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,0 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,1 mill kr).

URALUR EIENDOM AS is registered as a limited company in Sirdal, Agder with organisation number 932487055. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Oppfølging og utleie av forretningsbygg og eiendom. Andre oppgaver som står i nær tilknytning foran nevnte.”. The most recent filed accounts, for the 2025 financial year, show NOK 222,000 in revenue and NOK −1.1m in operating profit.

Key figures · 2025

Revenue
NOK 222,000
Operating profit
NOK −1.1m
Equity
NOK −2.0m

Financial health · 2025

Liquidity
2.52
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-53.6%
Weak
Equity as a share of total capital

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

Who owns URALUR EIENDOM AS?

URALUR HOLDING AS
URALUR EIENDOM AS
NOK 222,000 rev. · NOK −1.1m profit

URALUR EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about URALUR EIENDOM AS

Who owns URALUR EIENDOM AS?

URALUR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of URALUR EIENDOM AS?

URALUR EIENDOM AS had revenue of NOK 222,000 in 2025.

Where is URALUR EIENDOM AS based?

URALUR EIENDOM AS has its business address in Tjørhom.

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.