BIZTRAC BETA
COMPANY REGISTER PROFILE
917840199 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

SATHEO HOLDING AS

Org. no. 917840199 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −28,000
Equity NOK 1.6m
Incorporated 2016
Share capital NOK 30,000

Signals

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

SATHEO HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 917840199. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets formål er kjøp og salg av MAT&DRIKKE, samt aksjeoppkjøp i lignende bedrifter og formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −28,000
▼ −15 %
Equity
NOK 1.6m
▼ −24 %
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
284.89
Very good
Current assets ÷ current liabilities
Profitability
4.2%
Weak
Return on total assets
Solidity
99.6%
Very good
Equity as a share of total capital

Who owns SATHEO HOLDING AS?

SATHEO HOLDING AS
NOK 0 rev. · NOK −28,000 profit

SATHEO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SATHEO HOLDING AS

Who owns SATHEO HOLDING AS?

KENNETH STØRSETH SØRGÅRD is the largest registered owner, with 100.0%.

What is the revenue of SATHEO HOLDING AS?

SATHEO HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of SATHEO HOLDING AS?

Kenneth Størseth Sørgård is registered as general manager of SATHEO HOLDING AS.

Where is SATHEO HOLDING AS based?

SATHEO HOLDING 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 25.08.2026.

Report a problem

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