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

SDS INVEST AS

Org. no. 923182055 Limited company (AS) Namsos Incorporated 2019 Active
Ownership graph ↗
Equity NOK 413,000
Incorporated 2019
Share capital NOK 100,000

SDS INVEST AS is registered as a limited company in Namsos, Trøndelag with organisation number 923182055. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper, kjøp salg av eiendom og det som faller naturlig innenfor dette.”.

Key figures · 2025

Equity
NOK 413,000
▲ +3 %
Est. value
NOK 293,000

Financial health · 2025

Liquidity
58.28
Very good
Current assets ÷ current liabilities
Profitability
3.7%
Weak
Return on total assets
Solidity
98.7%
Very good
Equity as a share of total capital

Who owns SDS INVEST AS?

SDS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SDS INVEST AS own?

SDS INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SDS INVEST AS

Who owns SDS INVEST AS?

SVEN DANIEL SLETTEN is the largest registered owner, with 100.0%.

Who is the general manager of SDS INVEST AS?

Sven Daniel Sletten is registered as general manager of SDS INVEST AS.

Where is SDS INVEST AS based?

SDS INVEST AS has its business address in Fosslandsosen.

Property

Business address Aglenvegen 1472, 7819 Fosslandsosen
Cadastral unit 5007-61/15/0/0
Building Enebolig · 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.