BIZTRAC BETA
COMPANY REGISTER PROFILE
992242817 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Other captive investment companies

VARDEBAKKEN INVESTERINGSSELSKAB AS

Org. no. 992242817 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 2.2m
Incorporated 2008
Share capital NOK 100,000

VARDEBAKKEN INVESTERINGSSELSKAB AS is registered as a limited company in Oslo, Oslo with organisation number 992242817. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Finansiell virksomhet. Det vil si deltagelse i andre virksomheter, handel med aksjer og andre verdipapirer.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 2.2m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns VARDEBAKKEN INVESTERINGSSELSKAB AS?

TORJE STORAKER
VARDEBAKKEN INVESTERINGSSELSKAB AS
· NOK 0 profit

VARDEBAKKEN INVESTERINGSSELSKAB AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VARDEBAKKEN INVESTERINGSSELSKAB AS own?

VARDEBAKKEN INVESTERINGSSELSKAB AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VARDEBAKKEN INVESTERINGSSELSKAB AS

Who owns VARDEBAKKEN INVESTERINGSSELSKAB AS?

TORJE STORAKER is the largest registered owner, with 100.0%.

Who is the general manager of VARDEBAKKEN INVESTERINGSSELSKAB AS?

Torje Storaker is registered as general manager of VARDEBAKKEN INVESTERINGSSELSKAB AS.

Where is VARDEBAKKEN INVESTERINGSSELSKAB AS based?

VARDEBAKKEN INVESTERINGSSELSKAB 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 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.