BIZTRAC BETA
Civil engineering activities

SIV ING ØYVIND STOKKE AS

Org. no. 995689898 Limited company (AS) Tønsberg Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 1.1m
Equity NOK 2.6m
Incorporated 2010
Share capital NOK 100,000

SIV ING ØYVIND STOKKE AS is registered as a limited company in Tønsberg, Vestfold with organisation number 995689898. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er byggteknisk konsulentvirksomhet, eiendomsrådgivning og taksering av fast eiendom samt hva dermed står i forbindelse, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 1.1m
Equity
NOK 2.6m
Est. value
NOK 5.1m

Financial health · 2024

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

Who owns SIV ING ØYVIND STOKKE AS?

ØYVIND STOKKE
SIV ING ØYVIND STOKKE AS
NOK 2.9m rev. · NOK 1.1m profit

SIV ING ØYVIND STOKKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIV ING ØYVIND STOKKE AS

Who owns SIV ING ØYVIND STOKKE AS?

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

What is the revenue of SIV ING ØYVIND STOKKE AS?

SIV ING ØYVIND STOKKE AS had revenue of NOK 2.9m in 2025.

Who is the general manager of SIV ING ØYVIND STOKKE AS?

Øyvind Stokke is registered as general manager of SIV ING ØYVIND STOKKE AS.

Where is SIV ING ØYVIND STOKKE AS based?

SIV ING ØYVIND STOKKE 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.