BIZTRAC BETA
Arts creation activities in literature

EIK - PELAGOS AS

Org. no. 921027745 Limited company (AS) Tønsberg Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 138,000
Operating profit NOK 86,000
Equity NOK 2.6m
Incorporated 2018
Share capital NOK 30,000

EIK - PELAGOS AS is registered as a limited company in Tønsberg, Vestfold with organisation number 921027745. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Økonomisk rådgivning av enhver art. Forfatterrettigheter og annen virksomhet knyttet til publisering av fagstoff. Investering i andre foretak ved eierandeler/aksjer og finansiering/utlån. Annen næringsdrift.”. The most recent filed accounts, for the 2025 financial year, show NOK 138,000 in revenue and NOK 86,000 in operating profit.

Key figures · 2025

Revenue
NOK 138,000
Operating profit
NOK 86,000
Equity
NOK 2.6m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns EIK - PELAGOS AS?

KJELL MAGNE BAKSAAS
EIK - PELAGOS AS
NOK 138,000 rev. · NOK 86,000 profit

EIK - PELAGOS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIK - PELAGOS AS own?

EIK - PELAGOS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about EIK - PELAGOS AS

Who owns EIK - PELAGOS AS?

KJELL MAGNE BAKSAAS is the largest registered owner, with 100.0%.

What is the revenue of EIK - PELAGOS AS?

EIK - PELAGOS AS had revenue of NOK 138,000 in 2025.

Where is EIK - PELAGOS AS based?

EIK - PELAGOS AS has its business address in Tønsberg.

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.