BIZTRAC BETA
Development of building projects

AALTVEDT UTVIKLING AS

Org. no. 926818678 Limited company (AS) Skien Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 17.8m
Operating profit NOK 521,000
Equity NOK 171,000
Incorporated 2021
Share capital NOK 60,000

Signals

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

AALTVEDT UTVIKLING AS is registered as a limited company in Skien, Telemark with organisation number 926818678. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Å drive bygg- og entreprenørvirksomhet, industriell utviklingsvirksomhet, salgsvirksomhet samt dertil hørende virksomhet, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.8m in revenue and NOK 521,000 in operating profit.

Key figures · 2024

Revenue
NOK 17.8m
Operating profit
NOK 521,000
Equity
NOK 171,000
Est. value
NOK 1.0m

Financial health · 2024

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.4%
Not satisfactory
Equity as a share of total capital

Who owns AALTVEDT UTVIKLING AS?

INVESTA - AS
AALTVEDT UTVIKLING AS
NOK 17.8m rev. · NOK 521,000 profit

AALTVEDT UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AALTVEDT UTVIKLING AS

Who owns AALTVEDT UTVIKLING AS?

INVESTA - AS is the largest registered owner, with 50.0%.

What is the revenue of AALTVEDT UTVIKLING AS?

AALTVEDT UTVIKLING AS had revenue of NOK 17.8m in 2024.

Where is AALTVEDT UTVIKLING AS based?

AALTVEDT UTVIKLING AS has its business address in Skien.

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.