BIZTRAC BETA
Rental and operating of own or leased real estate

ALLSTAD UTVIKLINGSTOMTER AS

Org. no. 933730158 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −19,000
Equity NOK 18,000
Incorporated 2024
Share capital NOK 300,000

Signals

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

ALLSTAD UTVIKLINGSTOMTER AS is registered as a limited company in Oslo, Oslo with organisation number 933730158. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Investering og forvaltning av fast eiendom og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −19,000
Equity
NOK 18,000
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.0%
Weak
Equity as a share of total capital

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

Who owns ALLSTAD UTVIKLINGSTOMTER AS?

ALLSTAD AS
ALLSTAD UTVIKLINGSTOMTER AS
NOK 1.1m rev. · NOK −19,000 profit

ALLSTAD UTVIKLINGSTOMTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALLSTAD UTVIKLINGSTOMTER AS

Who owns ALLSTAD UTVIKLINGSTOMTER AS?

ALLSTAD AS is the largest registered owner, with 100.0%.

What is the revenue of ALLSTAD UTVIKLINGSTOMTER AS?

ALLSTAD UTVIKLINGSTOMTER AS had revenue of NOK 1.1m in 2024.

Where is ALLSTAD UTVIKLINGSTOMTER AS based?

ALLSTAD UTVIKLINGSTOMTER 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.