biztrac. BETA
COMPANY REGISTER PROFILE
929616022 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

S.O. SAELE AS

Org. no. 929616022 Limited company (AS) Kristiansand Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2022
Share capital NOK 30,000

S.O. SAELE AS is registered as a limited company in Kristiansand, Agder with organisation number 929616022. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investere i selskaper, rådgivning og konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Former names: AFAS 180722-26 AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
▲ +0 %
Est. value
NOK 35,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
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.O. SAELE AS?

S.O. SAELE AS
NOK 0 rev. · NOK 0 profit

S.O. SAELE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does S.O. SAELE AS own?

S.O. SAELE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about S.O. SAELE AS

Who owns S.O. SAELE AS?

Steffen Oliver Sæle is the largest registered owner, with 100.0%.

What is the revenue of S.O. SAELE AS?

S.O. SAELE AS had revenue of NOK 0 in 2025.

Who is the general manager of S.O. SAELE AS?

Steffen Oliver Sæle is registered as general manager of S.O. SAELE AS.

Where is S.O. SAELE AS based?

S.O. SAELE AS has its business address in Kristiansand S.

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.