BIZTRAC BETA
Site preparation

NO DIG VESTFOLD AS

Org. no. 921359721 Limited company (AS) Larvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 9.4m
Operating profit NOK −1.5m
Equity NOK 5.0m
Incorporated 2018
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,5 mill kr).

NO DIG VESTFOLD AS is registered as a limited company in Larvik, Vestfold with organisation number 921359721. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2018. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Maskinentreprenørvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK −1.5m in operating profit.

Key figures · 2025

Revenue
NOK 9.4m
Operating profit
NOK −1.5m
Equity
NOK 5.0m
Est. value
NOK 5.2m

Financial health · 2025

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

Who owns NO DIG VESTFOLD AS?

H & K SANDNES AS
NO DIG VESTFOLD AS
NOK 9.4m rev. · NOK −1.5m profit

NO DIG VESTFOLD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NO DIG VESTFOLD AS own?

NO DIG VESTFOLD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NO DIG VESTFOLD AS

Who owns NO DIG VESTFOLD AS?

H & K SANDNES AS is the largest registered owner, with 100.0%.

What is the revenue of NO DIG VESTFOLD AS?

NO DIG VESTFOLD AS had revenue of NOK 9.4m in 2025.

Who is the general manager of NO DIG VESTFOLD AS?

Halvard Eikås is registered as general manager of NO DIG VESTFOLD AS.

Where is NO DIG VESTFOLD AS based?

NO DIG VESTFOLD AS has its business address in Larvik.

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.