BIZTRAC BETA
Accounting and bookkeeping

DØVIK REGNSKAP AS

Org. no. 934911318 Limited company (AS) Tønsberg Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 440,000
Operating profit NOK 22,000
Equity NOK 42,000
Incorporated 2025
Share capital NOK 30,000

DØVIK REGNSKAP AS is registered as a limited company in Tønsberg, Vestfold with organisation number 934911318. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Regnskaps- og rådgivningstjenester, samt salg av de tjenester som naturlig hører inn under dette, investeringsvirksomhet, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 440,000 in revenue and NOK 22,000 in operating profit.

Key figures · 2025

Revenue
NOK 440,000
Operating profit
NOK 22,000
Equity
NOK 42,000
Est. value
NOK 131,000

Financial health · 2025

Liquidity
0.81
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DØVIK REGNSKAP AS?

TORGEIR DØVIK HOLDING AS
DØVIK REGNSKAP AS
NOK 440,000 rev. · NOK 22,000 profit

DØVIK REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DØVIK REGNSKAP AS

Who owns DØVIK REGNSKAP AS?

TORGEIR DØVIK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of DØVIK REGNSKAP AS?

DØVIK REGNSKAP AS had revenue of NOK 440,000 in 2025.

Who is the general manager of DØVIK REGNSKAP AS?

Torgeir Døvik is registered as general manager of DØVIK REGNSKAP AS.

Where is DØVIK REGNSKAP AS based?

DØVIK REGNSKAP AS has its business address in Undrumsdal.

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.