BIZTRAC BETA
Other captive investment companies

STERLINGVOSS AS

Org. no. 916368453 Limited company (AS) Lier Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −8,000
Equity NOK 3.6m
Incorporated 2015
Share capital NOK 36,000

Signals

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

STERLINGVOSS AS is registered as a limited company in Lier, Buskerud with organisation number 916368453. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 36,000, divided into 3600 shares. The company's stated purpose is: “Eie aksjer/andeler i andre selskaper samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 3.6m
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns STERLINGVOSS AS?

MARIUS HÆHRE ØDEGAARD
STERLINGVOSS AS
NOK 0 rev. · NOK −8,000 profit

STERLINGVOSS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STERLINGVOSS AS own?

STERLINGVOSS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STERLINGVOSS AS

Who owns STERLINGVOSS AS?

MARIUS HÆHRE ØDEGAARD is the largest registered owner, with 100.0%.

What is the revenue of STERLINGVOSS AS?

STERLINGVOSS AS had revenue of NOK 0 in 2024.

Who is the general manager of STERLINGVOSS AS?

Marius Hæhre Ødegaard is registered as general manager of STERLINGVOSS AS.

Where is STERLINGVOSS AS based?

STERLINGVOSS AS has its business address in Lier.

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.