BIZTRAC BETA
Other technical consultancy

STEENSNÆS INVEST AS

Org. no. 922903336 Limited company (AS) Lillestrøm Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK −4,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−4k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

STEENSNÆS INVEST AS is registered as a limited company in Lillestrøm, Akershus with organisation number 922903336. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Generell investeringsvirksomhet, herunder investering i verdipapirer, valuta, eiendommer, andeler, etc., samt delta i eller eie selskaper med beslektet virksomhet”.

Key figures · 2024

Operating profit
NOK −10,000
Equity
NOK −4,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STEENSNÆS INVEST AS?

ANDRÉ STEENSNÆS
STEENSNÆS INVEST AS
· NOK −10,000 profit

STEENSNÆS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STEENSNÆS INVEST AS own?

STEENSNÆS INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about STEENSNÆS INVEST AS

Who owns STEENSNÆS INVEST AS?

ANDRÉ STEENSNÆS is the largest registered owner, with 100.0%.

Who is the general manager of STEENSNÆS INVEST AS?

André Steensnæs is registered as general manager of STEENSNÆS INVEST AS.

Where is STEENSNÆS INVEST AS based?

STEENSNÆS INVEST AS has its business address in Kjeller.

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.