biztrac. BETA
COMPANY REGISTER PROFILE
928140474 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

STEENINVEST AS

Org. no. 928140474 Limited company (AS) Trondheim Incorporated 2021 Active
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 19,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

STEENINVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928140474. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bedriftsrådgivning, investering i selskaper samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
▼ −286 %
Equity
NOK 19,000
▼ −43 %
Est. value
NOK 22,000

Financial health · 2025

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

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

Who owns STEENINVEST AS?

STEENINVEST AS
NOK 0 rev. · NOK −14,000 profit

STEENINVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STEENINVEST AS own?

STEENINVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STEENINVEST AS

Who owns STEENINVEST AS?

Sigurd Emil Iden Steen is the largest registered owner, with 100.0%.

What is the revenue of STEENINVEST AS?

STEENINVEST AS had revenue of NOK 0 in 2025.

Where is STEENINVEST AS based?

STEENINVEST AS has its business address in Trondheim.

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.