BIZTRAC BETA
COMPANY REGISTER PROFILE
977116740 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Education at other colleges

HØGSKOLESTIFTELSEN I KONGSVINGER

Org. no. 977116740 Foundation (STI) Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 29.5m
Operating profit NOK 142,000
Equity NOK 18.9m
Incorporated 1990
Employees 14
Share capital NOK 100,000

HØGSKOLESTIFTELSEN I KONGSVINGER is registered as a foundation with organisation number 977116740. The business is classified under education at other colleges (NACE 85.403). The company was incorporated in 1990 and has 14 registered employees. Registered share capital is NOK 100,000. The most recent filed accounts, for the 2025 financial year, show NOK 29.5m in revenue and NOK 142,000 in operating profit.

Former names: STIFTELSEN FOR HØGSKOLEUTD I KONGSVINGER, STIFTELSEN FOR HØGSKOLEUTDANNING I KONGSVINGER

Key figures · 2025

Revenue
NOK 29.5m
Operating profit
NOK 142,000
Equity
NOK 18.9m
Est. value
NOK 12.6m

Financial health · 2025

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

Who owns HØGSKOLESTIFTELSEN I KONGSVINGER?

No shareholders are registered for HØGSKOLESTIFTELSEN I KONGSVINGER in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does HØGSKOLESTIFTELSEN I KONGSVINGER own?

HØGSKOLESTIFTELSEN I KONGSVINGER holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about HØGSKOLESTIFTELSEN I KONGSVINGER

What is the revenue of HØGSKOLESTIFTELSEN I KONGSVINGER?

HØGSKOLESTIFTELSEN I KONGSVINGER had revenue of NOK 29.5m in 2025.

Who is the general manager of HØGSKOLESTIFTELSEN I KONGSVINGER?

Bjørn Vegard Herlyng is registered as general manager of HØGSKOLESTIFTELSEN I KONGSVINGER.

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.