BIZTRAC BETA
Other captive investment companies

SSE INVEST AS

Org. no. 997732227 Limited company (AS) Lier Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 4.2m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

SSE INVEST AS is registered as a limited company in Lier, Buskerud with organisation number 997732227. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder å eie andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 4.2m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns SSE INVEST AS?

STIAN SEVERIN EDVARDSEN
SSE INVEST AS
NOK 0 rev. · NOK −10,000 profit

SSE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SSE INVEST AS own?

SSE INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SSE INVEST AS

Who owns SSE INVEST AS?

STIAN SEVERIN EDVARDSEN is the largest registered owner, with 100.0%.

What is the revenue of SSE INVEST AS?

SSE INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of SSE INVEST AS?

Stian Severin Edvardsen is registered as general manager of SSE INVEST AS.

Where is SSE INVEST AS based?

SSE INVEST AS has its business address in Lierskogen.

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.