biztrac. BETA
COMPANY REGISTER PROFILE
922709068 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

S-F HOLDING AS

Org. no. 922709068 Limited company (AS) Sunnfjord Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 25,000
Operating profit NOK 7,000
Equity NOK 344,000
Incorporated 2019
Share capital NOK 250,000

S-F HOLDING AS is registered as a limited company in Sunnfjord, Vestland with organisation number 922709068. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapir, samt annen virksomhet som faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 25,000 in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 25,000
▼ −37 %
Operating profit
NOK 7,000
▼ −73 %
Equity
NOK 344,000
▲ +1 %
Est. value
NOK 210,000

Financial health · 2025

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

Who owns S-F HOLDING AS?

S-F HOLDING AS
NOK 25,000 rev. · NOK 7,000 profit

S-F HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does S-F HOLDING AS own?

S-F HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about S-F HOLDING AS

Who owns S-F HOLDING AS?

Steinar Fonn is the largest registered owner, with 100.0%.

What is the revenue of S-F HOLDING AS?

S-F HOLDING AS had revenue of NOK 25,000 in 2025.

Who is the general manager of S-F HOLDING AS?

Steinar Fonn is registered as general manager of S-F HOLDING AS.

Where is S-F HOLDING AS based?

S-F HOLDING AS has its business address in Førde.

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.