BIZTRAC BETA
Computer programming activities

BIBLIOTEK-SYSTEMER A/S

Org. no. 946944483 Limited company (AS) Larvik Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 45.2m
Operating profit NOK 8.6m
Equity NOK 5.7m
Incorporated 1988
Employees 26
Share capital NOK 1.0m

BIBLIOTEK-SYSTEMER A/S is registered as a limited company in Larvik, Vestfold with organisation number 946944483. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 1988 and has 26 registered employees. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Salg av edb-utstyr og programvare, rådgivning og konsulentvirksomhet og hva dermed står i for- bindelse, herunder deltakelse i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 45.2m in revenue and NOK 8.6m in operating profit.

Key figures · 2025

Revenue
NOK 45.2m
Operating profit
NOK 8.6m
Equity
NOK 5.7m
Est. value
NOK 52.6m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.1%
Good
Equity as a share of total capital

Who owns BIBLIOTEK-SYSTEMER A/S?

OPIO INVEST AS
BIBLIOTEK-SYSTEMER A/S
NOK 45.2m rev. · NOK 8.6m profit

BIBLIOTEK-SYSTEMER A/S has 16 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIBLIOTEK-SYSTEMER A/S

Who owns BIBLIOTEK-SYSTEMER A/S?

OPIO INVEST AS is the largest registered owner, with 70.0%.

What is the revenue of BIBLIOTEK-SYSTEMER A/S?

BIBLIOTEK-SYSTEMER A/S had revenue of NOK 45.2m in 2025.

Who is the general manager of BIBLIOTEK-SYSTEMER A/S?

Ola Thori Kogstad is registered as general manager of BIBLIOTEK-SYSTEMER A/S.

Where is BIBLIOTEK-SYSTEMER A/S based?

BIBLIOTEK-SYSTEMER A/S has its business address in Larvik.

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.