BIZTRAC BETA
COMPANY REGISTER PROFILE
992614390 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Activities of business and employers membership organisations

NYSKAPINGSFONDET SOGN&FJORDANE STI

Org. no. 992614390 Foundation (STI) Bergen Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 182,000
Equity NOK 1.5m
Incorporated 2008
Share capital NOK 200,000

NYSKAPINGSFONDET SOGN&FJORDANE STI is registered as a foundation in Bergen, Vestland with organisation number 992614390. The business is classified under activities of business and employers membership organisations (NACE 94.110). The company was incorporated in 2008. Registered share capital is NOK 200,000. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 182,000 in operating profit.

Former names: SPAREBANKEN VESTS NÆRINGSSTIFTELSE FOR SOGN OG FJORDANE, SPAREBANKEN VESTS NÆRINGSFOND REGION SOGN OG FJORDANE, SPAREBANKEN VESTS NÆRINGSFOND REGION SOGN OG FJORDANE STI, SPAREBANKEN NORGE`S NÆRINGSFOND REGION SOGN OG FJORDANE

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 182,000
Equity
NOK 1.5m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns NYSKAPINGSFONDET SOGN&FJORDANE STI?

No shareholders are registered for NYSKAPINGSFONDET SOGN&FJORDANE STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about NYSKAPINGSFONDET SOGN&FJORDANE STI

What is the revenue of NYSKAPINGSFONDET SOGN&FJORDANE STI?

NYSKAPINGSFONDET SOGN&FJORDANE STI had revenue of NOK 3.1m in 2025.

Where is NYSKAPINGSFONDET SOGN&FJORDANE STI based?

NYSKAPINGSFONDET SOGN&FJORDANE STI has its business address in Bergen.

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.