BIZTRAC BETA
Auditing

BDT VIKEN AS

Org. no. 980995151 Limited company (AS) Horten Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 66.5m
Operating profit NOK 5.7m
Equity NOK 15.0m
Incorporated 1999
Employees 47
Share capital NOK 154,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BDT VIKEN AS is registered as a limited company in Horten, Vestfold with organisation number 980995151. The business is classified under auditing (NACE 69.201). The company was incorporated in 1999 and has 47 registered employees. Registered share capital is NOK 154,000, divided into 154 shares. The company's stated purpose is: “Revisjon og konsulentvirksomhet samt å føre regnskap for andre, eiendomsbesittelse og deltakelse i andre selskap og hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 66.5m in revenue and NOK 5.7m in operating profit.

Key figures · 2025

Revenue
NOK 66.5m
Operating profit
NOK 5.7m
Equity
NOK 15.0m
Est. value
NOK 37.5m

Financial health · 2025

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

Who owns BDT VIKEN AS?

BDT VIKEN HOLDING AS
BDT VIKEN AS
NOK 66.5m rev. · NOK 5.7m profit

BDT VIKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BDT VIKEN AS

Who owns BDT VIKEN AS?

BDT VIKEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BDT VIKEN AS?

BDT VIKEN AS had revenue of NOK 66.5m in 2025.

Who is the general manager of BDT VIKEN AS?

Per Edwin Engen is registered as general manager of BDT VIKEN AS.

Where is BDT VIKEN AS based?

BDT VIKEN AS has its business address in Horten.

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.