BIZTRAC BETA
Site preparation

SVERRE HAVIK AS

Org. no. 956888719 Limited company (AS) Namsos Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 28.3m
Operating profit NOK 2.3m
Equity NOK 12.2m
Incorporated 1989
Employees 18
Share capital NOK 100,000

SVERRE HAVIK AS is registered as a limited company in Namsos, Trøndelag with organisation number 956888719. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1989 and has 18 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Entreprenørvirksomhet. Selskapet kan også delta i annen økonomisk virksomhet som styre til enhver tid finner økonomisk forsvarlig.”. The most recent filed accounts, for the 2025 financial year, show NOK 28.3m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 28.3m
Operating profit
NOK 2.3m
Equity
NOK 12.2m
Est. value
NOK 11.1m

Financial health · 2025

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

Who owns SVERRE HAVIK AS?

SVEIN OLA HAVIK
SVERRE HAVIK AS
NOK 28.3m rev. · NOK 2.3m profit

SVERRE HAVIK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SVERRE HAVIK AS own?

SVERRE HAVIK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SVERRE HAVIK AS

Who owns SVERRE HAVIK AS?

SVEIN OLA HAVIK is the largest registered owner, with 96.0%.

What is the revenue of SVERRE HAVIK AS?

SVERRE HAVIK AS had revenue of NOK 28.3m in 2025.

Who is the general manager of SVERRE HAVIK AS?

Svein Ola Havik is registered as general manager of SVERRE HAVIK AS.

Where is SVERRE HAVIK AS based?

SVERRE HAVIK AS has its business address in Spillum.

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.