BIZTRAC BETA
COMPANY REGISTER PROFILE
844316402 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Accounting and bookkeeping

OPTIMAL BEDRIFTSRÅDGIVNING AS

Org. no. 844316402 Limited company (AS) Bergen Incorporated 1987 Active
Ownership graph ↗
Operating profit NOK −67,000
Equity NOK 62.0m
Incorporated 1987
Share capital NOK 506,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−67k kr).

OPTIMAL BEDRIFTSRÅDGIVNING AS is registered as a limited company in Bergen, Vestland with organisation number 844316402. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1987. Registered share capital is NOK 506,000, divided into 22000 shares. The company's stated purpose is: “Salg av konsulenttjenester samt investering i aksjer og andeler i andre selskap.”.

Key figures · 2025

Operating profit
NOK −67,000
Equity
NOK 62.0m
Est. value
NOK 172.7m

Financial health · 2025

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

Who owns OPTIMAL BEDRIFTSRÅDGIVNING AS?

OPTIMAL BEDRIFTSRÅDGIVNING AS
· NOK −67,000 profit

OPTIMAL BEDRIFTSRÅDGIVNING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OPTIMAL BEDRIFTSRÅDGIVNING AS own?

OPTIMAL BEDRIFTSRÅDGIVNING AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about OPTIMAL BEDRIFTSRÅDGIVNING AS

Who owns OPTIMAL BEDRIFTSRÅDGIVNING AS?

DAG DØSKELAND is the largest registered owner, with 100.0%.

Who is the general manager of OPTIMAL BEDRIFTSRÅDGIVNING AS?

Dag Døskeland is registered as general manager of OPTIMAL BEDRIFTSRÅDGIVNING AS.

Where is OPTIMAL BEDRIFTSRÅDGIVNING AS based?

OPTIMAL BEDRIFTSRÅDGIVNING AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.