BIZTRAC BETA
Other education activities

INNLANDET KOMPETANSESENTER AS

Org. no. 921193025 Limited company (AS) Ringsaker Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 5.7m
Operating profit NOK 95,000
Equity NOK 2.0m
Incorporated 2018
Share capital NOK 30,000

INNLANDET KOMPETANSESENTER AS is registered as a limited company in Ringsaker, Innlandet with organisation number 921193025. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fagopplæring og kursing av lærlinger og fagarbeidere, samt alt som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.7m in revenue and NOK 95,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.7m
Operating profit
NOK 95,000
Equity
NOK 2.0m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns INNLANDET KOMPETANSESENTER AS?

THOMAS BERGERSEN
INNLANDET KOMPETANSESENTER AS
NOK 5.7m rev. · NOK 95,000 profit

INNLANDET KOMPETANSESENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INNLANDET KOMPETANSESENTER AS

Who owns INNLANDET KOMPETANSESENTER AS?

THOMAS BERGERSEN is the largest registered owner, with 100.0%.

What is the revenue of INNLANDET KOMPETANSESENTER AS?

INNLANDET KOMPETANSESENTER AS had revenue of NOK 5.7m in 2024.

Who is the general manager of INNLANDET KOMPETANSESENTER AS?

Thomas Bergersen is registered as general manager of INNLANDET KOMPETANSESENTER AS.

Where is INNLANDET KOMPETANSESENTER AS based?

INNLANDET KOMPETANSESENTER AS has its business address in Stavsjø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

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