BIZTRAC BETA
Development of building projects

VESTSKOGEN K6 AS

Org. no. 933245950 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −15,000
Equity NOK 1.1m
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).
  • Nylig endring 2026-03-08 Adresseendring registrert 2026-03-08.

VESTSKOGEN K6 AS is registered as a limited company in Oslo, Oslo with organisation number 933245950. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 1.1m
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns VESTSKOGEN K6 AS?

ASKER EIENDOMSSELSKAP AS
VESTSKOGEN K6 AS
NOK 0 rev. · NOK −15,000 profit

VESTSKOGEN K6 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTSKOGEN K6 AS

Who owns VESTSKOGEN K6 AS?

ASKER EIENDOMSSELSKAP AS is the largest registered owner, with 100.0%.

What is the revenue of VESTSKOGEN K6 AS?

VESTSKOGEN K6 AS had revenue of NOK 0 in 2024.

Who is the general manager of VESTSKOGEN K6 AS?

Rageb Petterson is registered as general manager of VESTSKOGEN K6 AS.

Where is VESTSKOGEN K6 AS based?

VESTSKOGEN K6 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.