biztrac. BETA
COMPANY REGISTER PROFILE
929861086 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

STEEP INVEST AS

Org. no. 929861086 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11
Equity NOK 3.5m
Incorporated 2022
Share capital NOK 300,000

Signals

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

STEEP INVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 929861086. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Investeringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11
Equity
NOK 3.5m
▲ +1062 %
Est. value
NOK 22.9m

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
147.3%
Very good
Return on total assets
Solidity
93.6%
Very good
Equity as a share of total capital

Who owns STEEP INVEST AS?

STEEP INVEST AS
NOK 0 rev. · NOK −11 profit

STEEP INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STEEP INVEST AS own?

STEEP INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STEEP INVEST AS

Who owns STEEP INVEST AS?

Steffen Robertsen is the largest registered owner, with 100.0%.

What is the revenue of STEEP INVEST AS?

STEEP INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of STEEP INVEST AS?

Steffen Robertsen is registered as general manager of STEEP INVEST AS.

Where is STEEP INVEST AS based?

STEEP INVEST AS has its business address in Drammen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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