BIZTRAC BETA
Publishing of books

ORKANA FORLAG AS

Org. no. 967191809 Limited company (AS) Vestvågøy Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 8.3m
Operating profit NOK −25,000
Equity NOK 657,000
Incorporated 1993
Employees 5
Share capital NOK 500,000

Signals

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

ORKANA FORLAG AS is registered as a limited company in Vestvågøy, Nordland with organisation number 967191809. The business is classified under publishing of books (NACE 58.110). The company was incorporated in 1993 and has 5 registered employees. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Utgi bøker og annet skriftlig materiell, fortrinnsvis med utgangspunkt i kystkulturen, samt dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.3m in revenue and NOK −25,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.3m
Operating profit
NOK −25,000
Equity
NOK 657,000
Est. value
NOK 14.3m

Financial health · 2024

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

Who owns ORKANA FORLAG AS?

ELISABETH JOHANSEN
ORKANA FORLAG AS
NOK 8.3m rev. · NOK −25,000 profit

ORKANA FORLAG AS has 17 registered shareholders:

All shareholders and roles →

Which companies does ORKANA FORLAG AS own?

ORKANA FORLAG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ORKANA FORLAG AS

Who owns ORKANA FORLAG AS?

ELISABETH JOHANSEN is the largest registered owner, with 49.5%.

What is the revenue of ORKANA FORLAG AS?

ORKANA FORLAG AS had revenue of NOK 8.3m in 2024.

Where is ORKANA FORLAG AS based?

ORKANA FORLAG AS has its business address in Stamsund.

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.