BIZTRAC BETA
Arts creation activities in literature

ÅPEN BOK AS

Org. no. 929872134 Limited company (AS) Sandefjord Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 3,000
Operating profit NOK −3,000
Equity NOK 139,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

ÅPEN BOK AS is registered as a limited company in Sandefjord, Vestfold with organisation number 929872134. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Forlagsvirksomhet, handel og produksjon, samt eventuelt deltagelse med eierinteresser i annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 3,000
Operating profit
NOK −3,000
Equity
NOK 139,000
Est. value
NOK 63,000

Financial health · 2024

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

Who owns ÅPEN BOK AS?

HASLE KAPITAL AS
ÅPEN BOK AS
NOK 3,000 rev. · NOK −3,000 profit

ÅPEN BOK AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ÅPEN BOK AS er morselskap for 3 datterselskaper:

Frequently asked questions about ÅPEN BOK AS

Who owns ÅPEN BOK AS?

HASLE KAPITAL AS is the largest registered owner, with 100.0%.

What is the revenue of ÅPEN BOK AS?

ÅPEN BOK AS had revenue of NOK 3,000 in 2024.

Who is the general manager of ÅPEN BOK AS?

Marte Hasle is registered as general manager of ÅPEN BOK AS.

Where is ÅPEN BOK AS based?

ÅPEN BOK AS has its business address in Sandefjord.

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.