BIZTRAC BETA
Uoppgitt

SILSETH AS

Org. no. 921896271 Limited company (AS) Gjemnes Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 40,000
Operating profit NOK −95,000
Equity NOK 30.0m
Incorporated 2018
Share capital NOK 2.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−95k kr).

SILSETH AS is registered as a limited company in Gjemnes, Møre og Romsdal with organisation number 921896271. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 2.5m, divided into 33625 shares. The company's stated purpose is: “Investere i aksjer og selskaper med økonomisk formål. Selskapet skal forøvrig kunne drive virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 40,000 in revenue and NOK −95,000 in operating profit.

Key figures · 2024

Revenue
NOK 40,000
Operating profit
NOK −95,000
Equity
NOK 30.0m
Est. value
NOK 26.8m

Financial health · 2024

Liquidity
22.68
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
96.1%
Very good
Equity as a share of total capital

Who owns SILSETH AS?

ODDBJØRN SILSETH
SILSETH AS
NOK 40,000 rev. · NOK −95,000 profit

SILSETH AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SILSETH AS own?

SILSETH AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SILSETH AS

Who owns SILSETH AS?

ODDBJØRN SILSETH is the largest registered owner, with 100.0%.

What is the revenue of SILSETH AS?

SILSETH AS had revenue of NOK 40,000 in 2024.

Who is the general manager of SILSETH AS?

Oddbjørn Silseth is registered as general manager of SILSETH AS.

Where is SILSETH AS based?

SILSETH AS has its business address in Batnfjordsøra.

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.