BIZTRAC BETA
COMPANY REGISTER PROFILE
934146190 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

S.STEEN INVEST AS

Org. no. 934146190 Limited company (AS) Tynset Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 19,000
Incorporated 2024
Share capital NOK 30,000

S.STEEN INVEST AS is registered as a limited company in Tynset, Innlandet with organisation number 934146190. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Eie aksjer og investere i virksomheter av enhver art.”.

Key figures · 2025

Operating profit
NOK 0
▲ +100 %
Equity
NOK 19,000
▲ +0 %
Est. value
NOK 23,000

Financial health · 2025

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

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

Who owns S.STEEN INVEST AS?

S.STEEN INVEST AS
· NOK 0 profit

S.STEEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about S.STEEN INVEST AS

Who owns S.STEEN INVEST AS?

SONDRE STEEN is the largest registered owner, with 100.0%.

Who is the general manager of S.STEEN INVEST AS?

Sondre Steen is registered as general manager of S.STEEN INVEST AS.

Where is S.STEEN INVEST AS based?

S.STEEN INVEST AS has its business address in Tynset.

Property

Business address Nebyveien 108, 2500 Tynset
Cadastral unit 3427-75/211/0/0
Building Verkstedbygning · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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