BIZTRAC BETA
Buying and selling of own real estate

VEDLAUSFJELL AS

Org. no. 998235723 Limited company (AS) Nissedal Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 719,000
Equity NOK 1.7m
Incorporated 2012
Share capital NOK 30,000

VEDLAUSFJELL AS is registered as a limited company in Nissedal, Telemark with organisation number 998235723. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av hyttetomter, opparbeidelse og drift av tilhørende infrastruktur, samt andre tjenester som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 719,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 719,000
Equity
NOK 1.7m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns VEDLAUSFJELL AS?

STEIN SKÅLI
VEDLAUSFJELL AS
NOK 1.1m rev. · NOK 719,000 profit

VEDLAUSFJELL AS has 4 registered shareholders:

All shareholders and roles →

Which companies does VEDLAUSFJELL AS own?

VEDLAUSFJELL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VEDLAUSFJELL AS

Who owns VEDLAUSFJELL AS?

STEIN SKÅLI is the largest registered owner, with 25.0%.

What is the revenue of VEDLAUSFJELL AS?

VEDLAUSFJELL AS had revenue of NOK 1.1m in 2024.

Who is the general manager of VEDLAUSFJELL AS?

Tore Skåli is registered as general manager of VEDLAUSFJELL AS.

Where is VEDLAUSFJELL AS based?

VEDLAUSFJELL AS has its business address in Åmli.

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.