BIZTRAC BETA
Development of building projects

AURSKOG UTVIKLING AS

Org. no. 923193375 Limited company (AS) Aurskog-Høland Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −12,000
Equity NOK 503,000
Incorporated 2019
Share capital NOK 740,000

Signals

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

AURSKOG UTVIKLING AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 923193375. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 740,000, divided into 740 shares. The company's stated purpose is: “Kjøp, salg, utvikling, utbygging, forvaltning og utleie av eiendom, samt hva naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 503,000
Est. value
NOK 459,000

Financial health · 2024

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

Who owns AURSKOG UTVIKLING AS?

AURSKOG HOLDING AS
AURSKOG UTVIKLING AS
NOK 0 rev. · NOK −12,000 profit

AURSKOG UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AURSKOG UTVIKLING AS

Who owns AURSKOG UTVIKLING AS?

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

What is the revenue of AURSKOG UTVIKLING AS?

AURSKOG UTVIKLING AS had revenue of NOK 0 in 2024.

Who is the general manager of AURSKOG UTVIKLING AS?

Steinar Englund is registered as general manager of AURSKOG UTVIKLING AS.

Where is AURSKOG UTVIKLING AS based?

AURSKOG UTVIKLING AS has its business address in Aurskog.

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.