BIZTRAC BETA
Intermediation service activities for specialised retail sale

BOOKIS AS

Org. no. 917690979 Limited company (AS) Tromsø Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 56.0m
Operating profit NOK 333,000
Equity NOK 4.7m
Incorporated 2016
Employees 6
Share capital NOK 972,000

BOOKIS AS is registered as a limited company in Tromsø, Troms with organisation number 917690979. The business is classified under intermediation service activities for specialised retail sale (NACE 47.920). The company was incorporated in 2016 and has 6 registered employees. Registered share capital is NOK 972,000, divided into 972358 shares. The company's stated purpose is: “Selskapets virksomhet er utvikling og drift av digitale forretningskonsepter, samt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 56.0m in revenue and NOK 333,000 in operating profit.

Key figures · 2025

Revenue
NOK 56.0m
Operating profit
NOK 333,000
Equity
NOK 4.7m
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns BOOKIS AS?

DRUUUSERS AS
BOOKIS AS
NOK 56.0m rev. · NOK 333,000 profit

BOOKIS AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does BOOKIS AS own?

BOOKIS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BOOKIS AS

Who owns BOOKIS AS?

DRUUUSERS AS is the largest registered owner, with 44.5%.

What is the revenue of BOOKIS AS?

BOOKIS AS had revenue of NOK 56.0m in 2025.

Who is the general manager of BOOKIS AS?

Arne-Morten Willumsen is registered as general manager of BOOKIS AS.

Where is BOOKIS AS based?

BOOKIS AS has its business address in Tromsø.

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.