BIZTRAC BETA
Accounting and bookkeeping

ØYVIND BAKKEN AS

Org. no. 989967681 Limited company (AS) Larvik Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 304,000
Operating profit NOK 103,000
Equity NOK 2.7m
Incorporated 2006
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-09 Aksjekapital registrert 2026-06-09.

ØYVIND BAKKEN AS is registered as a limited company in Larvik, Vestfold with organisation number 989967681. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å foreta investering i finansielle instrumenter, utføre regnskapstjenester og økonomisk rådgivning overfor virksomheter og privatpersoner og det som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 304,000 in revenue and NOK 103,000 in operating profit.

Key figures · 2024

Revenue
NOK 304,000
Operating profit
NOK 103,000
Equity
NOK 2.7m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns ØYVIND BAKKEN AS?

ØYVIND BAKKEN
ØYVIND BAKKEN AS
NOK 304,000 rev. · NOK 103,000 profit

ØYVIND BAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØYVIND BAKKEN AS own?

ØYVIND BAKKEN AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about ØYVIND BAKKEN AS

Who owns ØYVIND BAKKEN AS?

ØYVIND BAKKEN is the largest registered owner, with 100.0%.

What is the revenue of ØYVIND BAKKEN AS?

ØYVIND BAKKEN AS had revenue of NOK 304,000 in 2024.

Where is ØYVIND BAKKEN AS based?

ØYVIND BAKKEN AS has its business address in Helgeroa.

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.