biztrac. BETA
COMPANY REGISTER PROFILE
914983428 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Compulsory dissolution UPDATED 03.10.2026
⚠NESVIK MASKINSALG AS is registered as “Compulsory dissolution” with the Brønnøysund Register Centre.
Wholesale of mining, construction and civil engineering machinery

NESVIK MASKINSALG AS

Org. no. 914983428 Limited company (AS) Hå Incorporated 2015 Compulsory dissolution
Operating profit NOK −27,000
Equity NOK 66,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Tvangsoppløsning Selskapet er under tvangsoppløsning.

NESVIK MASKINSALG AS is registered as a limited company in Hå, Rogaland with organisation number 914983428. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Å forhandle salg av anleggsmaskiner og utstyr samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −27,000
▼ −80 %
Equity
NOK 66,000
▼ −80 %

Financial health · 2024

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
19.5%
Weak
Equity as a share of total capital

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

Who owns NESVIK MASKINSALG AS?

NESVIK MASKINSALG AS has 3 registered shareholders:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about NESVIK MASKINSALG AS

Who owns NESVIK MASKINSALG AS?

Leiv Nesvik is the largest registered owner, with 50.0%.

Where is NESVIK MASKINSALG AS based?

NESVIK MASKINSALG AS has its business address in Brusand.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.