biztrac. BETA
COMPANY REGISTER PROFILE
818087772 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

NESVIK INVEST AS

Org. no. 818087772 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 17,000
Incorporated 2016
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

NESVIK INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 818087772. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Selskapet skal fungere som et holdingselskap, og skal forvalte sine verdier gjennom oppkjøp, investeringer og alt som naturlig faller inn under dette.”.

Key figures · 2025

Operating profit
NOK −8,000
▼ −25 %
Equity
NOK 17,000
▼ −33 %
Est. value
NOK 16,000

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
-14.8%
Not satisfactory
Return on total assets
Solidity
34.1%
Weak
Equity as a share of total capital

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

Who owns NESVIK INVEST AS?

NESVIK INVEST AS
· NOK −8,000 profit

NESVIK INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NESVIK INVEST AS own?

NESVIK INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NESVIK INVEST AS

Who owns NESVIK INVEST AS?

Thomas André Nesvik is the largest registered owner, with 100.0%.

Who is the general manager of NESVIK INVEST AS?

Thomas André Nesvik is registered as general manager of NESVIK INVEST AS.

Where is NESVIK INVEST AS based?

NESVIK INVEST AS has its business address in Oslo.

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.