BIZTRAC BETA
Logging

NOGVA HOLDING AS

Org. no. 925347698 Limited company (AS) Tønsberg Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −23,000
Equity NOK −973,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−973k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23k kr).

NOGVA HOLDING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 925347698. The business is classified under logging (NACE 02.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer, samt investeringer i virksomheter av enhver art og det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK −973,000

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-132.8%
Weak
Equity as a share of total capital

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

Who owns NOGVA HOLDING AS?

BØRGE NOGVA
NOGVA HOLDING AS
NOK 0 rev. · NOK −23,000 profit

NOGVA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NOGVA HOLDING AS own?

NOGVA HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NOGVA HOLDING AS

Who owns NOGVA HOLDING AS?

BØRGE NOGVA is the largest registered owner, with 100.0%.

What is the revenue of NOGVA HOLDING AS?

NOGVA HOLDING AS had revenue of NOK 0 in 2024.

Where is NOGVA HOLDING AS based?

NOGVA HOLDING AS has its business address in Tolvsrød.

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.